Details
-
Story
-
Status: Closed
-
Minor
-
Resolution: Completed
-
None
-
AppSec Iteration 54, AppSec Iteration 55, AppSec Iteration 56, AppSec Iteration 57, AppSec Iteration 58, AppSec Iteration 59, AppSec Iteration 60, AppSec Iteration 61, AppSec Iteration 62, AppSec Iteration 63, AppSec Iteration 64, AppSec Iteration 65
Description
Motivation
Sometimes it is necessary to use UUID instead of email address to avoid conflicting users across systems and also largely to avoid the issue of people being able to update their email addresses and it not breaking across systems.
Acceptance Criteria
- As an Instance Administrator, I can map an assertion attribute containing a UUID to a user field, and also match users on this.
Attachments
Issue Links
- causes
-
LPS-132640 Version increase required in modules-semantic-versioning-jdk8/0/8
- Closed
-
LPS-132754 Failed upgrade process for module com.liferay.saml.persistence.service from 7310 with DB2 and SQLServer
- Closed
-
LPS-133349 NPE is thrown when navigating to second SP
- Closed
-
LPS-143370 Updating samlNameIdValue does not flag previous record for deletion
- Closed
-
LPS-143253 We can't store long EntityID information for SAML
- Verified
- demands
-
LPS-151388 Apply processing SPI to SamlIdpSpConnections
-
- Open
-
- is a dependency of
-
LPS-125272 As an Instance Administrator, I want a SAML assertion attribute to be mapped to screenName even if it differs from NameID
-
- Closed
-
- is related to
-
LPS-123459 Design how to handle changed user identifiers in configured IdP in a general way
-
- Closed
-
-
LPS-138777 Create a test plan for SAML attribute mapping
-
- Closed
-
- relates
-
LPS-133175 Unsaved Liferay.AutoFields rows are lost when reloading page after validation error
- Closed
-
LPS-140307 Cannot match LDAP users on UUID attribute
- Closed
-
LRDOCS-9354 User Document for SAML enhancements
-
- Closed
-
-
LPS-133543 Automate firstName and lastName matching and LDAP combination based on LPS-123218
-
- Closed
-
- Testing discovered
-
LPS-133168 When a newly added User Attribute Mapping field selected as 'Use to Match Users', the User Resolution doesn't autoselect 'Match Using a Specific SAML Attribute Mapping'
- Closed
-
LPS-133176 Order of the User Attribute Mapping fields are change after a Page refresh
- Closed
-
LPS-133178 SAML login with using UUID SAML attribute is not matching user with changed email address at Service Provider
- Closed
-
LPS-133362 No indicator of the default User Resolution option when a new IDP connection is added to SP
- Closed
-
LPS-133379 Empty User attribute field can be saved for User Matching at SP site's IDP connection form
- Closed
-
LPS-133380 No SamlSpSession exists with the key error during sign out from SP site
- Closed
-
LPS-133386 Unsupported SAML attribute mapping could be selected for User Matching by Instance Administrators
- Closed
-
LPS-133548 User Resolution option isn't selected after saving configuration
- Closed
-
LPS-133638 SAML SP SLO doesn't work properly when logged in more than one SP
- Closed
-
LPS-137159 First/last name can't be selected for user matching while LDAP import is enabled
- Closed
-
LPS-137141 User attributes only partially sync
- Verified
- links to
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...