Allow the Use of Nonstandard Email Domains
Apache components included in the AM appliance prevent the use of nonstandard email domains, such as .bank, .law, and .sms. AM allows the nonstandard .local domain.
To use other nonstandard domains, you must edit the AM ims.properties file on each primary and replica instance.
Before you begin
The rsaadmin operating system password for the primary instance is required.
Procedure
- Log on to the primary instance appliance with the User ID rsaadmin and the current operating system password:
- On a hardware appliance, an Amazon Web Services appliance, or an Azure appliance, log on to the appliance using the SSH client.
- On a VMware virtual appliance, log on to the appliance using an SSH client or the VMware vSphere client.
- On a Hyper-V virtual appliance, log on to the appliance using an SSH client, the Hyper-V System Center Virtual Machine Manager Console, or the Hyper-V Manager.
- Change directories:
cd /opt/rsa/am/utils/resources
- In a text editor, such as the vi editor, open the ims.properties file.
- If the validDomainList line does not exist, only the .local nonstandard domain is supported, and you must add validDomainList to support additional nonstandard domains:
validDomainList=.nonstandard;.local;
Where nonstandard is the name of the nonstandard domain. For example, to support a .sms and a .local email domain, you would enter validDomainList=.sms;.local;
You can add more than one nonstandard domain. Separate each name with a semicolon.
- Save your changes. For example, in the vi editor, type :wq!.
- Change directories:
cd /opt/rsa/am/server
- Restart Authentication Manager services:
./rsaserv restart all
The nonstandard domains are listed in /opt/rsa/am/utils/resources/ims.properties.
- The ims.properties file is not replicated. If you promote a replica instance, you must repeat this procedure, unless you prepare for promotion by repeating these steps on each Authentication Manager instance in your deployment.
After you finish
If you have a web tier, you must update each web-tier server. For instructions, see Update the Web Tier to Allow the Use of Nonstandard Email Domains.
Related Articles
Use of KBA in UAT environment 29Number of Views Plus (+) characters changed to (%2b) in email text sent from Workflow Email Nodes in SecurID Governance & Lifecycle 25Number of Views Error occured in RSA Federated Identity Manger (FIM) 4.1 'Unable to verify the signature value' error when processing asse… 26Number of Views Assign RADIUS User Attributes to Users 12Number of Views Allow a User to Authenticate Without an RSA SecurID PIN 54Number of Views
Trending Articles
Change Requests stuck in the AFX Fulfillment Handler Workflow Node and Workflows Stalled in RSA Identity Governance & Life… Collector Stuck in Data Collection Phase with "Sent Request to Agent Hosting the Collector" RSA Authentication Manager 8.9 Patches and Hotfixes Readme How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Workflows stuck in AFX fulfillment and/or Provisioning nodes in RSA Identity Governance & Lifecycle