If the SSO operation is successful for an ABL session, it:

  1. Makes a deep copy of the user credentials from the security token into the ABL session context.
  2. Records the session's user ID and login session ID for internal use by auditing (and other internal functions), effectively setting the identity for the session.
  3. Repeatedly executes the SSO operation in an attempt to set the same identity in each OpenEdge database connection currently established in the session, (see Process for a successful SSO to an OpenEdge database connection on page 1).
    Note: In an ABL session, a database connection can be programmed to lock out the ability to set its identity when setting the session identity.