Configuring Realms (UI)
You create and configure realms through the AM console, starting from the Realms page.
AM requires cookies for all configured realms when using DNS aliases. For example, if you install AM in the domain,
openam.example.net and have realms,
security.example.com then you must configure cookie domains for
.example.com. You can set up cookie domains for each realm by following the procedure in "To Configure DNS Aliases for Accessing a Realm".
This section has the following procedures:
You can create a new realm through the AM console as described below, or by using the ssoadm create-realm command:
In the AM console, go to the Realms page, and click New Realm. The New Realm page appears. Complete the form to configure the realm.
In the Name field, enter a descriptive name for the realm.
Realm names must not match any of the following:
Existing realm names.
Existing realm aliases.
Names of AM REST endpoints.
The Active button is enabled by default.
If you configure the realm to be inactive, then users cannot use it to authenticate or be granted access to protected resources.
In the Parent field, enter the parent of your realm.
Default: the top level realm (/).
In the Realm Aliases field, enter a simple text alias to represent the realm.
In the DNS Aliases field, enter fully qualified domain names (FQDN) that can be used to represent the realm.
A DNS alias is not related to the CNAME record used in DNS database zones. In other words, the option shown in the AM console does not conform to the definition of DNS aliases described in RFC 2219.
Entering a DNS alias in the AM console also applies required changes to the advanced server property
For more information, see "To Configure DNS Aliases for Accessing a Realm".
To enable client-based sessions for the realm, toggle the Use Client-based Sessions switch. For more information on sessions, see Introducing Sessions.
Click Create to save your configuration.
You can configure realms to be associated with specific fully qualified domain names (FQDN).
For example, consider a deployment with the following characteristics:
The FQDN for AM and the top level realm is
AM also services
realm2.example.com. In other words, AM receives all HTTP(S) connections for these host names. Perhaps they share an IP address, or AM listens on all interfaces.
Without applying DNS aliases to the relevant realm, when a user visits
http://realm1.example.com:8080/openam, AM redirects that user to the top level realm,
https://openam.example.com:8443/openam. If the authenticating user is present only in
realm1, then authentication fails even with correct credentials.
If no DNS alias is configured for a realm,
realm1 users must visit URLs such as
https://openam.example.com:8443/openam/XUI/?realm=/realm1#login. This format of URL reveals the top level realm, and exposes extra information about the service.
Configure DNS aliases for realms to prevent redirection and having to expose the top level realm domain by performing the following steps:
Realm aliases must be unique within an AM instance, and cannot contain the characters
\, or spaces.
Add the domains that AM services to the list of domains that created cookies will be applicable to, as follows:
In the AM console, go to Configure > Global Services > Platform.
In Cookie Domains, enter the domains that AM will service.
For example, if you installed AM at
openam.example.net, and intend to have realms associated with FQDNs
realm2.example.com, then the Cookie Domains list would include
Set the FQDN for each realm as follows:
Navigate to Realms > Realm Name, and then click Properties.
In DNS Aliases, enter one or more FQDN values for the realm.
Save your changes.
(Optional) Adding DNS aliases by using the AM console also adds FQDN mappings to the AM server.
To verify these have been created perform the following steps:
Navigate to Configure > Server Defaults > Advanced.
For each FQDN DNS alias configured, verify the existence of a property named
com.sun.identity.server.fqdnMap[Realm FQDN]with a property value of Realm FQDN.
For example, the property may be called
com.sun.identity.server.fqdnMap[realm1.example.com]with a value of
If the property does not exist or needs to be changed, manually create the property for each FQDN DNS alias.
Save your changes.
The new realm aliases take effect immediately, it is not necessary to restart AM. You can now use a URL such as
realm1, rather than