Benjamin KAHANE
- Updated
Notes:
The following steps need to be performed within the Keycloak admin account.
Mouse hover on highlighted dropdown and click on Add realm button.
Enter realm name.
Enter realm general details.
Import the Flex SAML Metadata.
Verify the highlighted field on next screen.
On successful import of Flex SAML Metadata, a client will get created with default values.
Expand Fine Grain SAML Endpoint Configuration.
Few configuration parts need to be updated & rest of the default values should be left as same.
Highlighted URLs should be updated as per given below in table.
| Name | URL |
| Valid Redirect URIs | like https://{account}.{your-flex-deployment.com}/login/saml/SSO |
| Assertion Consumer Service POST Binding URL | like https://{account}.{your-flex-deployment.com}/login/saml/SSO |
| Logout Service POST Binding URL | like https://{account}.{your-flex-deployment.com}/login/saml/SingleLogout |
| Logout Service Redirect Binding URL | like https://{account}.{your-flex-deployment.com}/login/saml/SingleLogout |
| Artifact Binding URL | like https://{account}.{your-flex-deployment.com}/login/saml/SSO |
Save the configuration.
Please follow the User Attributes And Claims to see what all are required user attributes & claims need
to be configured.
Navigate to mappers tab.
Note: Each mapper must be named in camelCase.
Add email mapper.
Add firstName mapper.
Add lastName mapper.
Add login mapper. This is optional mapper as per listed User Attributes And Claims.
Add flexAccountUuid mapper.
Note: Similarly the externalUniqueUserId mapper can be configured to user's profile with unique identifier value and defined as a mapper to make it available in SAML response.
Add groups mapper (This is optional and only required when Flex Group membership sync is enabled).
Now navigate back to Clients tab & verify that the newly configured client is present & enabled.
Navigate to the Users tab & click on the Add User button.
Enter user details.
Save and navigate back to the Users tab, and check that the user was successfully created.
Note If the new user does not appear in the list, click on the View all users button.
Navigate to Realm Settings.
Click on the link within the Endpoints section, entitled SAML 2.0 Identity Provider Metadata.
This will open an XML file in another tab. Copy the entire contents into an editor and modify it.
For Example:
<md:EntitiesDescriptorxmlns="urn:oasis:names:tc:SAML:2.0:metadata"xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"xmlns:ds="http://www.w3.org/2000/09/xmldsig#"Name="urn:keycloak"><md:EntityDescriptorxmlns="urn:oasis:names:tc:SAML:2.0:metadata"xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"xmlns:ds="http://www.w3.org/2000/09/xmldsig#"entityID="http://192.168.99.100:8080/auth/realms/FlexRealm">
<md:EntityDescriptorxmlns="urn:oasis:names:tc:SAML:2.0:metadata"xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"xmlns:ds="http://www.w3.org/2000/09/xmldsig#"entityID="http://192.168.99.100:8080/auth/realms/FlexRealm"Name="urn:keycloak">
Don’t forget to remove the closing </md:EntitiesDescriptor> tag to keep the XML valid!
Save the modified content somewhere for use in the Flex configuration steps below.
Note:
Verification of Keycloak SAML integration with Flex was performed using static test users only.
Comments
0 comments
Please sign in to leave a comment.