Update Duo Admin User Struct with available fields #52
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
jeffreyparker
requested changes
Apr 5, 2024
|
Thanks for the quick fixes! This looks good-to-go now. We avoid releasing on Fridays, and because of golang's "master is immediately released" nature, we'll approve/merge this in on Monday. |
jeffreyparker
approved these changes
Apr 8, 2024
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.
Description
Updating the Duo Admin API User structure to contain the updated structure fields. Currently Webauthn and U2F tokens are completely unretrievable via the API
How Has This Been Tested?
No tests existed for the previous functionality
Types of Changes