Configure Proxy Connector for Console Access

Overview

Step 1 - Configure SAML Application

Step 2 - Provide Metadata to Cirrus

Test the Integration

Overview

This document outlines the steps required to configure a Cirrus Bridge Proxy Connector for Console Access. This is for customers that are not InCommon members who need console access, for example a CAS Bridge or Slate Bridge customer. You will create a new SAML integration in your primary identity provider with the PC Bridge as the service provider. Your Cirrus Technical Implementation Lead will provide you with the values specific to your Bridge and you will follow the steps below to configure. 

Step 1 - Configure SAML Application

Add Application

In this step, you will add the Service Provider configuration. Your Technical Implementation Lead will provide you with the following information specific to your proxy connector bridge.

• Metadata url
• SP Entity ID (Audience URI)
• Single Sign-On/SAML ACS URL
• Single Logout URL

For identity providers that accept metadata, you should just need that. For others, you may need to manually configure and add the information above.

Configure Attributes

Next you will add the following attributes.

Step 2 - Provide Metadata to Cirrus

Copy the metadata url for the SAML Application created in the previous step. Then send to your Technical Implementation Lead. 

Test the Integration

Once you are notified that the metadata has been loaded, you can now test your integration. You will test by logging into the Cirrus Console or FreshDesk to test.If you run into any issues, please generate a SAML Trace and send to your Technical Implementation Lead.