-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add missing scope tags to connection options #269
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #269 +/- ##
=======================================
Coverage 94.78% 94.79%
=======================================
Files 46 46
Lines 8733 8738 +5
=======================================
+ Hits 8278 8283 +5
Misses 353 353
Partials 102 102
☔ View full report in Codecov by Sentry. |
@@ -861,6 +861,8 @@ type ConnectionOptionsAD struct { | |||
|
|||
UpstreamParams map[string]interface{} `json:"upstream_params,omitempty"` | |||
|
|||
Thumbprints *[]string `json:"thumbprints,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also seems to have been missed from the AD connection options type.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To note also that the SAML conn type has thumbprints defined as []interface{}
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the SAML property was added before the schema repo so we didn't know the type of it?
🔧 Changes
Through https://github.com/auth0/go-auth0/pull/263/files we introduced the
ExtGroups
andExtProfile
properties on theConnectionOptionsPingFederate
andConnectionOptionsSAML
, however the scope tag was missed. This PR addresses that.To note also that unfortunately now we have inconsistent ways of describing the same attribute accepted by the API:
ext_groups
ConnectionOptionsPingFederate.ExtGroups
ConnectionOptionsSAML.ExtGroups
ConnectionOptionsAzureAD.Groups
ConnectionOptionsGoogleApps.Groups
ext_profile
ConnectionOptionsPingFederate.ExtProfile
ConnectionOptionsSAML.ExtProfile
ConnectionOptionsGoogleApps.ExtendedProfile
ConnectionOptionsAzureAD.ExtendedProfile
📚 References
🔬 Testing
📝 Checklist