Check for Google Authenticator status #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Google Authenticator is not compatible with Duo as a post_auth provider. If enabled the crstate object will be undefined when the user authentication is passed to this script.
Post_Auth documentation recommends using authret['user'] when dealing with LDAP/AD. Not mentioned though is key re-negotiation can fail with username inconsistencies provided by user (client-side) unless you do an LDAP remap.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed that post_auth throws a NoneType exception at
if crstate.get('challenge'):if Google Authenticator is enabled. These changes allow for assumption of Globally enabled Google Auth with user/group disable property for transitioning to Duo as well as just mixing the two if required.