Previous Topic: What is Signon Processing?Next Topic: User Validation Processing


Identifying the User

Explicit Signon

When an explicit signon request is issued by executing the SIGNON task or linking to RHDCSNON, the user is identified by the user ID specified on the signon request. The password to be used for verification is also specified as part of the signon request.

Automatic Signon

During automatic signon, the user is identified by the authorization ID under which the application is being executed.

If the signon does not occur within the CA IDMS system, the executing user is extracted from the operating system by issuing the appropriate call to the integration services layer of the CA Common Services architecture.

When signon processing is initiated automatically, no password verification is performed by CA IDMS software. CA IDMS assumes that the user has already been validated by the environment within which the application is executing.

Default Signon

You can allow CA IDMS to perform a signon using a specific name when a security check request is issued and the user is not signed on. This is done by specifying DFLTSGN=YES and the DFLTUID parameter on the initial #SECRTT macro.

Note: For more information, see #SECRTT.