I would expect a 'modify' to only modify the user account, and if it wasn't there, to not create it. if you see otherwise i would open a ticket w/ support.
there is not a passwd strength checker in the CO, can you attach your bldeploy log from the target w/ the failure?
BBSA is definately adding user accounts even when I set the action on my BLPackage to Modify. It does this on Linux and Solaris. I'll open a ticket with support.
The password strength checker thing is my bad. It's Linux that doesn't like my password. I can just ignore the error message that Linux spits out when I'm setting my password using passwd. BBSA quite rightly doesn't ignore the message when I'm using a BLPackage to deploy a user account.
In case anyone is interested, BMC Support has created a Defect for the issue I found with Unix user account Add and Modify Actions in a BLPackage having identical behaviour. I look forward to the behaviour changing in a future release of BBSA.