CCC API v8.4.0.0

<back to all web services

PublicGetSSOUser

The following routes are available for this service:
GET/api/public/ssoReturn a list of services the user can login to.If both CollectionGuid and SiteGuid are specified, they need to match (ie. the Collection must be within the Site).
PublicGetSSOUser Parameters:
NameParameterData TypeRequiredDescription
ServiceGuidbodyGuidNoIf ServiceGuid is specified then the service to which the user can login is defined by it.
CollectionGuidbodyGuidNoIf CollectionGuid is specified then the services to which the user can login are within that collection
SiteGuidbodyGuidNoif SiteGuid is specified then the services to which the user can login are within that site
EmailAddressbodyStringYes
PublicGetSSOUserResponse Parameters:
NameParameterData TypeRequiredDescription
ResultsbodySSOUser[]No
CountbodyIntegerNo
BaseResponse Parameters:
NameParameterData TypeRequiredDescription
ResponseStatusformResponseStatusNo
SSOUser Parameters:
NameParameterData TypeRequiredDescription
ServiceGuidbodyGuidNo
ServiceStatusformServiceStatusNo

Allowable Values

  • Blocked
  • AccountCancelled
  • AccountSuspended
  • Provisioning
  • TrialExpired
  • TrialActive
  • DemoAccount
  • CertifiedSecure
ServiceNameformstringNo
ServiceCodeformstringNo
SsoEnabledbodyBooleanNo

Allowable Values

  • true
  • false
SsoProxyNameformstringNo
SsoProxyUrlformstringNo
SsoProxyLogoutUrlformstringNo
SsoProxyGuidbodyGuidNo
CollectionGuidbodyGuidNo
PrimaryDomainformstringNo
BrandingformDictionary<string, string>No
UrlsformDictionary<ServiceUrlType, string>No

Allowable Values

  • MessagingApi
  • Webmail
  • ToolbarServices
  • GatewaySettings
  • AdminConsole
  • SecMsgAPI
  • Webapp
  • IdProxy
  • IdProxyLogout
AuthenticatorsformList<Authenticator>No
EmailAddressformstringNo
IsAuthenticatedbodyBooleanNo

Allowable Values

  • true
  • false
Authenticator Parameters:
NameParameterData TypeRequiredDescription
NamebodyStringNo
DescriptionbodyStringNo
IdProviderGuidbodyGuidNo
IdPxLoginUrlbodyStringNo
UsedLastbodyBooleanNo

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

GET /api/public/sso HTTP/1.1 
Host: api.secure-messaging.com 
Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{
  "results": [
    {
      "serviceGuid": "00000000000000000000000000000000",
      "serviceStatus": "Blocked",
      "serviceName": "String",
      "serviceCode": "String",
      "ssoEnabled": false,
      "ssoProxyName": "String",
      "ssoProxyUrl": "String",
      "ssoProxyLogoutUrl": "String",
      "ssoProxyGuid": "00000000000000000000000000000000",
      "collectionGuid": "00000000000000000000000000000000",
      "primaryDomain": "String",
      "branding": {
        "String": "String"
      },
      "urls": {
        "MessagingApi": "String"
      },
      "authenticators": [
        {
          "name": "String",
          "description": "String",
          "idProviderGuid": "00000000000000000000000000000000",
          "idPxLoginUrl": "String",
          "usedLast": false
        }
      ],
      "emailAddress": "String",
      "isAuthenticated": false
    }
  ],
  "count": 0,
  "responseStatus": {
    "errorCode": "String",
    "message": "String",
    "stackTrace": "String",
    "errors": [
      {
        "errorCode": "String",
        "fieldName": "String",
        "message": "String",
        "meta": {
          "String": "String"
        }
      }
    ],
    "meta": {
      "String": "String"
    }
  }
}