Thank you for your interest in the Cirrus Identity offerings via the Azure AD Application Gallery!
 
 

Cirrus Identity Bridge

A cloud-hosted solution to streamline access with Azure AD!

SAML Bridge

The Cirrus SAML Bridge supports multilateral federation for Azure AD.  Federations, like eduGAIN (worldwide) or InCommon (USA), provide education and research services to institutions.  The Cirrus SAML Bridge is an alternative to installing and maintaining Shibboleth or simpleSAMLphp (SSP).  In some situations, the SAML Bridge is also an alternative to running ADFS.

Learn More

 

CAS Bridge

The Cirrus CAS Bridge allows CAS-authenticated applications to integrate with Azure AD.  CAS applications are common in many higher education environments.  The CAS Bridge is an alternative to installing and maintaining CAS.

 

Learn More

 

Bridge-horizontal

Cirrus Identity Bridge Products

 
Cirrus SAML Bridge: Supports multilateral federation required by trust federations. The Cirrus SAML Bridge can serve as a “federation adapter” between Azure AD and InCommon (United States), CAF (Canada), UK Federation or any eduGAIN (worldwide) federation.
Cirrus CAS Bridge: Provides authentication between your CAS-authenticated applications and SAML-authenticated Azure AD.   The CAS Bridge provides institutions time to transition and where possible, reconfigure applications to directly authenticate with SAML Azure AD.
DNS Add-On:  Avoids individually re-configuring existing service providers for a faster implementation that expedites the retirement of local software. A great solution for institutions that have an existing identity provider registered with a federation and/or many CAS services.

The Cirrus Bridge and DNS Add-On are cloud-hosted managed solutions that run in a highly redundant architecture!

 

What to Expect - Easy as 1-2-3:

1) Cirrus Introductory Meeting  

Deployment and integration of Cirrus Identity products requires the following:

  • Fill out the registration form below.
  • Cirrus will soon reach out to schedule an Introductory meeting.  In the Introductory meeting, Cirrus will review:  1) the information collected in the registration form, 2) discuss your requirements and review the Cirrus products needed, 3) review usage estimates. 
  • After the introductory meeting, Cirrus will provide a pricing proposal and start the contract/procurement processes outlined below.  
  • If your institution is a member of InCommon (United States) or another eduGAIN (worldwide) federation and you would like to log in to the Cirrus Console with your institution's login, you will need to ask your Identity Management team to set up trust with the Cirrus Identity console and release attributes upon authentication per instructions here: Log in to the Cirrus Console using your campus SAML Identity Provider

Feel free to email sales@cirrusidentity.com at any time if you need anything!

2) Contracting and Procurement 

After confirming our solutions meet your needs, Cirrus Identity will:

  • Send the Main Agreement and SaaS Order Form that confirms pricing.
  • Contracts, invoicing and billing will be handled as annual subscriptions by Cirrus Identity. 
  • Please note that some institutions take weeks to review contract agreements - please check with your procurement team.

3) Provisioning and Implementation

Once contracts have been returned by the institution, Cirrus Identity will:

  • Schedule an Implementation Kick-Off call and can begin provisioning the Bridge(s) and optional DNS Add-On. 
  • During the Kick-Off meeting, Cirrus will review:  1) Bridge metadata and optional DNS configuration needs and documentation for reference, 2) provide an overview of the Cirrus Administrative Console and 3) review the Cirrus support and service request process. 
  • After the Kick-Off meeting, Cirrus will schedule regular meetings with your team to guide you through the configuration of the Cirrus solutions with your application(s) and Identity Provider(s). Production deployment can take 3 weeks to several months depending on the complexity of the integration, and the availability of your team to work on the integration.

 

Registration Information