SyferLock Help Center

Login Workflow

Provides a high level workflow of the login process workflow

Login Sequence Diagram

Login Sequence Diagram

The various steps in the login process are:

  1. The user navigates to the Array AG login page URL and enters their user name and submits it.
    1. Array forwards proxied HTTPS request to GridGuard Server
  2. GridGuard performs a check to determine if the user is already registered. This check will come back positive for registered users
  3. GridGuard looks up user in Active Directory to determine if the user is a member of groups authorized to use a GridGuard (if such a group has been specified)
  4. Active Directory responds back to indicate if the user is a member of the group. For valid users, this will return back a successful return code
  5. GridGuard displays the login page with the grid
    1. Array forwards HTTP response to user's browser
  6. User enters their network password and GridPIN and submits page.
    1. Array proxies HTTPS request
  7. GridGuard loads user credential information.
  8. GridGuard verifies GridPIN. If user in not authorized or not found, the login will be presented but will never succeed.
  9. Gridguard creates a nonce.
  10. GridGuard logs login attempt to audit database.
  11. GridGuard sends back an HTML to the browser that is configured to automatically submit to Array AG once the page is loaded.
    1. Auto submitted form is proxied by the Array AG.
  12. The auto-submit for submits the username, password, and nonce id to the Array AG.
  13. The Array AG performs an LDAP bind against Active Directory to verify password.
  14. Active Directory responds back to indicate if the bind was successful. A successful bind indicates that the password was correct.
  15. Array AG performs an LDAP bind against GridGuard to verify the nonce.
  16. The LDAP server decrypts the nonce and replaced the nonce id in the password for the raw PIN. And deletes the nonce.
  17. GridGuard's LDAP server validates the bind in the user dn and raw PIN.
  18. GridGuard's LDAP server competes bind request with correct PIN and user DN.
  19. GridGuard's responds back to indicate that the bind was successful.
  20. User is now considered authenticated and Array AG provides the user access to the configured resources.

If either the password or the GridPIN authentication failed in this process, the user is automatically directed to the password incorrect page and denied access to the system.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk