Skip to content

Conversation

@dickerpulli
Copy link

In some use cases a secondary password is configured at the server. This secondary password is asked in the same form as the username and first password. Some customers, like mine, uses this with a secure token that must be filled into this secondary password field.

@aperomsik
Copy link

Since last Thursday my employer uses a second web page to prompt for a second password. I didn't think it would work with this patch... but it does! I guess the second page is optional if you provide both passwords with the first request.

In comments, perhaps you should not assume that the second password is the tokencode. For whatever reason my employer does it the other way around: tokencode first, then LDAP password.

@dickerpulli
Copy link
Author

That's nice andI'm glad to hearthat it works for you.
By the way: in comments I just said "i.e. a secure token"...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants