Default language.

AREA behavior when the RPC program number is 390695

These tables show BMC Remedy AR System authentication behavior for this configuration:

  • Authenticate Unregistered Users is selected
  • Cross Reference Blank Password is selected
  • External Authentication Server RPC Program Number is 390695

For information about understanding authentication methods in AR System, see Specifying-internal-and-external-authentication.

User does not exist in User form

Authentication chaining mode

Authentication behavior

Off

  • Authentication is performed using AREA LDAP. User information is retrieved from AREA LDAP.

ARS - AREA

  • Authentication is not performed using BMC Remedy AR System because the user does not exist in the User form.
  • Authentication is performed using AREA LDAP. If successful, user information is retrieved from AREA LDAP.

AREA - ARS

  • Authentication is performed using AREA LDAP. If successful user information is retrieved from AREA LDAP.
  • Authentication is not performed using BMC Remedy AR System because the user does not exist in the User form.

ARS - OS - AREA

  • Authentication is not performed using BMC Remedy AR System because the user does not exist in the User form.
  • Authentication is performed using OS authentication. If successful, user information is retrieved from the OS.
  • If OS authentication fails, user authentication is performed using AREA LDAP. If AREA LDAP authentication is successful, user information is retrieved from AREA LDAP.

ARS - AREA - OS

  • Authentication is not performed using BMC Remedy AR System because the user does not exist in the User form.
  • Authentication is performed using AREA LDAP. If successful, user information is retrieved from AREA LDAP.
  • If AREA LDAP authentication fails, the user is authenticated using OS authentication. If OS authentication is successful, user information is retrieved from the OS.

User exists with no password in User form

Authentication chaining mode

Authentication behavior

Off

  • Authentication is performed using AREA LDAP password. User information is retrieved from the User form.
  • Authentication process stops when it fails using AREA LDAP.

ARS - AREA

  • Authentication is performed using AREA LDAP password. User information is retrieved from User form.
  • Authentication process stops when it fails using AREA LDAP.

AREA - ARS

  • Authentication is performed using AREA LDAP. If successful, user information is retrieved from AREA LDAP. If AREA LDAP configuration does not contain all the information in the form, missing information is retrieved from the User_Cache.
  • If AREA LDAP authentication fails, authentication processing stops.

ARS - OS - AREA

  • User authentication is performed using AREA LDAP. If successful, user information is retrieved from BMC Remedy AR System.
  • If AREA LDAP authentication fails, the user is authenticated using OS authentication. If OS authentication is successful, user information is retrieved from BMC Remedy AR System.
  • The user is never authenticated using User form.

ARS - AREA - OS

  • User authentication is performed using AREA LDAP. If successful, user information is retrieved from BMC Remedy AR System.
  • If AREA LDAP authentication fails, the user is authenticated using OS authentication. If OS authentication is successful, user information is retrieved from BMC Remedy AR System.
  • The user is never authenticated using User form.

User exists with password in User form

Authentication chaining mode

Authentication behavior

Off

  • Authentication is performed using the AR System User Form. If successful, user information is retrieved from the User form.
  • If User form authentication fails, authentication is not attempted using AREA LDAP.

ARS - AREA

  • Authentication is performed using the AR System User form. If successful, user information is retrieved from the User form.
  • If User form authentication fails, AREA LDAP authentication is attempted. If AREA LDAP authentication is successful, user information is retrieved from AREA LDAP.

AREA - ARS

  • Authentication is performed using AREA LDAP. If successful, user information is retrieved from AREA LDAP.
  • If AREA LDAP authentication fails, authentication is attempted using User form. If User form authentication is successful, user information is retrieved from the User form.

ARS - OS - AREA

  • Authentication is performed using the AR System User form. If successful, user information is retrieved from the User form.
  • If BMC Remedy AR System authentication fails, OS authentication is attempted. If OS authentication is successful, user information is retrieved from the OS.
  • If OS authentication fails, AREA LDAP authentication is attempted. If AREA LDAP authentication is successful, user information is retrieved from AREA LDAP.

ARS - AREA - OS

  • Authentication is performed using the AR System User form. If successful, user information is retrieved from the User form.
  • If BMC Remedy AR System authentication fails, AREA LDAP authentication is attempted. If AREA LDAP authentication is successful, user information is retrieved from AREA LDAP.
  • If AREA LDAP authentication fails, OS authentication is attempted. If OS authentication is successful, user information is retrieved from the OS.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*