Table of Contents
Cirrus offers several options for authentication and silent login into our systems in addition to our standard user/password login process.
Directory Services
We allow a login for our management site using Directory Services (DS) providers (such as Active Directory).
To set it up, the Single Sign-On module must be active, and the domain, username, and password (optional) must be set in the Module Settings tab. Furthermore, every user who wishes to log in using Directory Services must also set the Username field on the Users Management page.
Once configured, the system will try to validate the username and password fields inputted on the login page against the DS server. If successful, the user will be automatically signed into the system. Otherwise, the system will try to validate the user/password field using the standard Cirrus credentials.
Ticket Authentication
We allow a login for our management site and some apps using a custom-signed ticket for authentication. The ticket is created using our Ticket API
The ticket must be signed by the sending party using our API. The signed ticket is then passed using either a query string or a POST parameter and verified by the system. If successful and the provided user identifiers are valid, a session cookie will be created and returned to the user. If an existing cookie is found, it will be overwritten and extended.
Note: A user with these parameters must be set up via the management site in advance. Tickets used to log into our management site must include the Business account name (brand) and the username. If the ticket is used to log in to different apps, it must include all the required parameters for that specific app. (For example, FirstName, LastName, Phone, email address, etc.)
Note: Once created, tickets are only valid for 60 seconds for the management system and 5 minutes for other applications