Configure authenticators and realms

Authenticators are defined within the realm that uses them.

Realms are defined in <realm> elements in authenticationConfig.xml. The <realms> element contains a separate <realm> subelement for each realm.

Modify realms using the authentication configuration editor.

The <realm> element has the following attributes:

Attribute	Description
name	Mandatory. The unique name by which the realm is referenced by the protected resources.
loginModule	Mandatory. The name of the login module used by the realm.

The <realm> element has the following subelements:

Element	Description
<className>	Mandatory. The class name of the authenticator. For details of the supported authenticators, see the following topics.
<parameter>	Optional. Represents the name-value pairs that are passed to the authenticator upon instantiation. This element might be displayed multiple times.
<onLoginUrl>	Optional. Defines the path to which the client is forwarded upon successful login. If this element is not specified, then depending on the authenticator type, either the current request processing is continued, or a saved request is restored.

• Implementing basic authenticators
  We can implement basic authentication in mobile applications.

• Implementing form-based authenticators
  We can authenticate users of mobile applications using a login form.

• Implementing custom authenticators
  We can use default MobileFirst login modules and authenticators, or customize our own.

• Header authenticator
  Description and syntax of the header authenticator.

• Persistent cookie authenticator
  Description and syntax of the persistent cookie authenticator.

• Implementing adapter-based authenticators
  We can authenticate users of mobile applications using an adapter-based authenticator.

• LTPA authenticator
  Description and syntax for the LTPA authenticator.

Parent topic: MobileFirst security framework