You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Need to be able to set the User ID Attribute Type on Azure AD Connections to oid to support SCIM. My existing connections that were provisioned through TF were all defaulted to sub.
Describe the ideal solution
One idea would be to extend the user_id_attribute used for samlp connections and allow either oid or sub for AzureAD connections.
Alternatives and current workarounds
None. Any update to the Connection will cause a null to be passed to the userid_attribute field which will reset the value back to sub - even though it retrieved the value as "oid" in the GET just before the PATCH.
Additional context
No response
The text was updated successfully, but these errors were encountered:
From an API view (GET https://tenant.eu.auth0.com/api/v2/connection) the userid_atrribute property is not visible until it has been explicitly set in some way. In our case, while investigating the issue, we set the value to oid and then back to sub via the console. If we then made an API call to view the resource we can see the the userid_attribute property and can see that it is set to sub.
The next time we perform a terraform apply the property gets set back to null. Any subsequent terraform plan shows an intention to set this back to sub but it stays as null when viewed via the API.
# module.terraform-auth0-tenant.auth0_connection.connections["connection_aad"] will be updated in-place
~ resource "auth0_connection" "connections" {
id = "<redacted>"
name = "<redacted>"
# (5 unchanged attributes hidden)
~ options {
+ user_id_attribute = "sub"
# (37 unchanged attributes hidden)
}
}
Plan: 0 to add, 1 to change, 0 to destroy.
We assume that despite this showing as null the underlying behaviour is sub.
Checklist
Describe the problem you'd like to have solved
Need to be able to set the User ID Attribute Type on Azure AD Connections to oid to support SCIM. My existing connections that were provisioned through TF were all defaulted to sub.
Describe the ideal solution
One idea would be to extend the user_id_attribute used for samlp connections and allow either oid or sub for AzureAD connections.
Alternatives and current workarounds
None. Any update to the Connection will cause a null to be passed to the userid_attribute field which will reset the value back to sub - even though it retrieved the value as "oid" in the GET just before the PATCH.
Additional context
No response
The text was updated successfully, but these errors were encountered: