Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

For most implementations, single sign-on is not necessary because CloudCard's secure login links provide excellent security with the least possible user friction, which increases user adoption.  However, there are many use cases for which SSO improves the user experience.

For our A+ customers, CloudCard can deploy an SSO Connector in our Cloud for SAML2 identity providers which includes CAS, Shibboleth, and ADFS.

Process:

  1. Install the metadata for our test SSO connector on your IdP.
  2. Create a test login account for CloudCard Support
  3. Securely communicate the following to CloudCard Support
    1. authentication credentials for the test login account
    2. the SAML attribute mapping for
      1. email address
      2. ID number*
      3. any custom fields if you want to provision or update users via SSO
  4. CloudCard will configure the test SSO connector.
  5. If applicable, CloudCard will request the creation the CNAME record that will point to the production SSO connector.
  6. CloudCard will deploy your production SSO connector.
  7. Install the production metadata in you production IdP.
  8. CloudCard will conduct final testing and configuration.

Simplified SSO Integration Diagram

DIY SSO:

Because CloudCard uses a stateless, token-based authentication protocol, implementing SSO on premises is relatively trivial.  For an example, check out the cloudcard-auth-csharp GitHub project. This command line project demonstrates how to consume the necessary API endpoints to retrieve auto-login links on a secured web page, so authenticated users on your site will automatically be logged into Online Photo Submission when they click the login link.  This project also demonstrates how to create/update users if necessary.

  • No labels