How to synchronize user accounts that do not have an email address to the SecurID Access Cloud Authentication Service
2 years ago
Originally Published: 2022-05-04
Article Number
000067905
Applies To
RSA Product Set: SecurID Access
RSA Product/Service Type: Cloud Authentication Service
Issue
The Email Address field on the Cloud Administration Console > Users > Identity Sources > Edit > Synchronize User Attributes page is used for multiple purposes and is set to mail by default. If the mail attribute is blank/not defined for a user in the identity source, then that user will not be synced to the Cloud Authentication Service.
Resolution
There are a few solutions to get users who do not have the mail attribute defined to be synced to the Cloud Authentication Service:
 
  • Option 1: If users who are currently synced to the Cloud Authentication Service from the identity source have the SAME value for their mail and userPrincipalName attributes, then the mapping of Email Address in the identity source configuration in the Cloud Administration Console can be changed from mail to userPrincipalName. This change would make it so users that are already synced are not affected (assuming their userPrincipalName is the same as their mail) and also allow users who do not have mail defined to be synced based on their userPrincipalName.
 
  • Option 2: If users who are currently synced to the Cloud Authentication Service from the identity source have a DIFFERENT value for their mail and userPrincipalName attributes, then an additional identity source can be added to the Cloud Authentication Service specifically for the users who do not have the mail attribute defined. In the new identity source's configuration, the Email Address field can be mapped to userPrincipalName.
Important: When adding and configuring the new identity source, it is importing to configure it so that users that are currently synced to any other identity source(s) configured with the Cloud Authentication Service will not end up being synced to this new identity source. 

 
  • Option 3: Define the mail attribute for the users in the identity source that do not currently have it defined but that need to be synced to the Cloud Authentication Service (the email addresses set in the mail attribute do not need to be "real" email addresses.)