Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

For

most

many implementations, single sign-on is not necessary because CloudCard's secure login links provide

excelent

excellent security with

the least possible

minimal user friction, which increases user adoption.  However,

in some cases SSO is required for IT compliance. 

Cloud SSO

CloudCard can implement SSO in the Cloud for most major identity providers

there are numerous use cases where SSO improves user experience while offering a scalable provisioning strategy.

As an implementation add-on, CloudCard can integrate our SSO Connector for any SAML2 identity provider (including CAS, Shibboleth, and ADFS

.  However, there are an associated implementation and annual service fees.

On-Premises SSO

Because CloudCard uses a stateless, token-based authentication protocol, implementing SSO on premises is relatively trivial. In most cases, CloudCard can provide an authentication connector for your organization to host on-premise.

Displayed to the right is a simplified diagram of how a CloudCard SSO Auth Connector works.  The authentication connector is highlighted in red.  The exact implementation of a connector (i.e. PHP, JavaScript, ColdFusion, Java) depends on the customer's preferences.

Below an example of a connector is displayed in pseudocode to further explain the process.

Code Block
languagejs
titleSample Connector
/**
 * This connector should run on the server - NOT in a webpage
 * or any other client-side technology.
 */
const CLOUDCARD_API_ACCESS_TOKEN // CloudCard provides this

// cardholder data
var cardholderEmail //required
var cardholderIDNumber //optional; but highly recommended
var customField1 //optional
car customField2 //optional

/**
 * This function loads cardholder data from the session,
 * a database, LDAP, or wherever is most convenient.
 */
function loadCardholderData () {
  // this is written by the customer
}

/**
 * sends a GET request to CloudCard to request to CloudCard 
 * requesting a cardholder by email address
 */
function getCardholder() {
  // see https://sharptop.atlassian.net/wiki/spaces/CCD/pages/15859788/Get+a+Person
}

Simplified SSO Integration Diagram

Image Removed

).

Process:

  1. Install the metadata for our test SSO connector on your IdP (preferably your test IDP if available).
  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 names for:
      1. email address
      2. ID number (generally an immutable identifier)
      3. any custom fields if you want to provision or update users via SSO
  4. CloudCard will configure the test SSO connector by installing your metadata on our system and then test the configuration. 
  5. If the test is successful, we will switch over to production.
  6. Install our production metadata in your production IdP.
  7. CloudCard will deploy your production SSO connector.
  8. CloudCard will conduct final testing and configuration.