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
Hi folks - we are happy users of the Auth0 provider, but couldn't find a way to set the user mapping on OIDC connections.
In the UI, it can be specified as follows:
However, the provider does not offer a field to set it. From browsing through the docs and Github issues, we saw that there is a similar field fields_map for SAML connections.
Interestingly, when applying a setting like the following, it succeeds, but the OIDC connection in the portal doesn't show any fields anymore (leaving the connection in a weird state, so we had to recreate it):
Thanks for raising this with us, you're correct that at the moment this field is lacking within the provider. We'll aim at adding support for it in the near future, however no ETA as to when. I'll circle back once I have an update. Appreciate your patience!
We have added support for this within the auth0_connection resource in the latest beta release. Please give it a try, and if you come across any issues, don't hesitate to reach out.
Checklist
Describe the problem you'd like to have solved
Hi folks - we are happy users of the Auth0 provider, but couldn't find a way to set the user mapping on OIDC connections.
In the UI, it can be specified as follows:
However, the provider does not offer a field to set it. From browsing through the docs and Github issues, we saw that there is a similar field
fields_map
for SAML connections.Interestingly, when applying a setting like the following, it succeeds, but the OIDC connection in the portal doesn't show any fields anymore (leaving the connection in a weird state, so we had to recreate it):
Describe the ideal solution
It would be nice if the
auth0_connection
resource would allow specifying the mapping. Example:Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: