-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.13.0 GA, 2.14.0 GA
-
5
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
The sentence "you can either configure the User Federation mapping to set the Email Verified attribute to true" is not currently possible:
https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.5/html/creating_the_developer_portal/authentication#rhsso
However, there is https://issues.jboss.org/browse/KEYCLOAK-8316 which once available in a GA released of Red Hat Single Sign-On will allow the same function but with a different configuration. Once this is available please update 3scale documentation with correct instructions to setup RH-SSO LDAP for this change. In the unreleased version this is done by setting "Trust Email" in the LDAP User Federation configuration, but maybe there will be changes before it's GAed.
Additionally, althought "in the client created previously for 3scale SSO integration configure a hardcoded claim, with the token name email_verified and the claim value set to true." technically works, it's not the correct way to do it. Unfortunately until KEYCLOAK-8316 is released it's the only option. So probably a good idea to suggest against this approach in the 3scale documentation once the LDAP provider "Trust Email" setting exists.
- relates to
-
THREESCALE-3642 Remove instructions to use LDAP mapper in RH-SSO integration
- Closed