Update integrations endpoint to v3 #38
Merged
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.
This updates the only reference to
/admin/v1/integrationsto/admin/v3/integrationssimilar to duosecurity/duo_client_python#282. It also includes changes to update to canonicalization v5.Description
Updates the
/admin/v1/integrationsreference tov3.Because the
v3endpoints require canonicalization 5, the larger change in this PR is updating the canonicalization to 5.Motivation and Context
The v3 integrations endpoints add a new
user_accessfield and change the behavior of thegroups_allowedfield.Previously the
groups_allowedfield by itself determined which users could authenticate with the application as described here. Now a third state has been added which allows no users to authenticate.Because of that, the
user_accessfield has been added to express this more cleanly, andgroups_allowedcan only be provided ifuser_access == "PERMITTED_GROUPS".How Has This Been Tested?
admin/v3/integrationsendpoint is working as expectedPOST admin/v1/groups,POST admin/v1/groups/:gkey,POST admin/v1/usershttps://gist.github.com/ckeif-duo/f86490d5380f6c57bfde4031e02e6795
Types of Changes