Details
-
Bug
-
Status: Verified
-
Resolution: Unresolved
-
Master
-
None
-
3
-
Security
Description
Steps to reproduce:
- Navigate to Identity Provider Connections and add Identity Provider
- Fill out necessary fields with relevant data
- Map two or more custom fields on the same attribute
- Try to save the mapping by clicking on the Save button
Actual result: We are navigated back to Identity Provider Connections page, as if the mapping got saved successfully, but upon opening the connection we see that mappings got deleted except for one!
Expected result: Mapping should not be saved and a warning message should be displayed, that mapping fields on the same attribute is not allowed.
Note: Check the attached snippets! (before, after)
Attachments
Issue Links
- Discovered while testing
-
LPS-128600 As an Instance Administrator, I want to configure mapping custom fields to data from SAML assertion when a user logs into the system
-
- Closed
-