Affects Version/s: Master
Component/s: Application Security > SAML
Currently, In the backend we only support matching on emailAddress, screenName and UUID, when LDAP import is disabled.
However, the UI didn't stop us to select other, non-supported fields for User Matching
Reproduction Steps (as described in LPS-133090 / TC-5 )
- Execute test steps in LPS-133090, Test Case 5
- Check tomcat error logs after the unsuccessful login
Using fields which are not supported for User Matching at the back end cause the following error log in to the console:
We should prevent the Instance administrators to mark fields which are not supported by backed, to use them as User Matching fields.