BTW; you cannot map literals
"email_verified": true
for some reason.
Any updates about this? users created with enterprise connection should be able to set as “email_verified”: true. right now it’s not possible like any other mapping! also as mentioned before, mapping “email_verified” attribute to literal true value is not setting the created users to verified after being created!
1 Like
Bump. Any updates on this? Being able to set the value of the email verified flag by default for SAML connections is a must.
Same for us as well. Plus, mapping to a “truthy” value breaks the Golang client that expects an actual boolean.
2 Likes
Ditto. This just broke one of our customers. The Auth0 Golang SDK requires “email_verified” to be a boolean, and will fail when it’s a string.
Bump. Not being able to set “email_verified” to true form SAML connections is breaking all of the Auth0 SDKs for reading users. We currently have to map to “http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier” but that is not a sufficient solution given the issue above.