Integrate with Password Policy module so the generated password meets policy requirement

I doubt it. Since this validates the password fields explicitly, I doubt they will work together. Are you asking if you can have Genpass follow the policies of Password Policy?

I would argue that the Genpass module should add the support needed for integration. Since this module only checks the provided password, the Genpass module should provide new passwords until the validation passes.

I won't be writing this patch, but somebody else is welcome to and re-open this issue, and I'll be happy to review it.

I have created sandbox module using which we can use Generate Password ("Genpass") module in conjunction with the Password Policy module.

This new module "Genpass Password policy" reads password criteria set by password policy module and generate new password.

https://www.drupal.org/sandbox/laxmang/2555131

@laxman.ghavte - could you post that as a patch? That's how Drupal issues become "needs review" is via the patch process. Moving back to active. I looked at the module and it seems it is incomplete with some elements hard-coded and has a bit of debug code left around in comments.

Another possible solution to this issue is to ensure that the generated password from genpass is very strong and therefore meets a lot of policies. I believe that would be handled by #2975168: Genpass 7.x-2.x. Am I naive to think about policies like that? :)

In my opinion, it should not be the responsibility of genpass to enforce "password policy" (hmm.. unless Policy becomes core maybe). Instead, genpass provides a hook (hook_password) which a dev can implement to provide his own policy-compliant password generator and a mechanism to select it as the method.

Such a password gen could easily call itself and check against Policy repetitively until it generates a compliant password. In practice, I got maybe 1 out of 4 password generations fail on me in genpass beta, and the new 1.0 branch promises to generate more complicated passwords out of the box:

> It should help to always pass basically any password policy since it's longer and has more variation in the kinds of characters that are included.

so should improve chances. This is to say that if you need it, implement such a hook, and if you find that it's running more than some low number of acceptable iterations, then re-open this issue.

I agree with the closure in #11. It seems this issue is largely solved by the new improved complexity of passwords that exists in 8.x-1.0 and in 7.x-2.x branch. If that proves not to be the case we can consider increasing the strength of those passwords further on a case-by-case basis.