Getting Started

Explore the components of SSO. Learn how to start using it and integrate with your client services and how to present it to end-users.

To allow end-users to authorize your client service to access their data, your service must integrate with SSO's Authorization API. This API supports OAuth 2.0 and OIDC industry standards, facilitating user authentication and client authorization. To access the API, you must first set up an SSO Account, which is straightforward and well-documented. To set-up an account you must first become a Verifier and have access to the Verifier Portal. To become one, visit the How to become a Verifier page.

Once set up, your service can integrate and start requesting Verifiable Credentials from end-users.

---

Main Components

There are two main components to the solution:

• SSO Dashboard: This is the central management console where an SSO account is set up and client configurations are managed. It provides tools to:

  • Monitor and download usage metrics and logs.

  • Manage clients and billing.

  • Set up advanced configurations for end-user authorizations in the future.

• Authorization API: This is the core of the SSO, enabling end-user authorization flows.

SSO Dashboard Overview

The SSO dashboard is integrated into the Verifier Dashboard, accessible with an active Verifier Account. To enable SSO, activate your account to create an SSO tenant linked to billing, API usage metrics, and logs. Each verifier account supports one SSO account.

Configuring Application Clients

Configure clients to access the Authorization API and set credential rules for end-users. Enhance user experience with features like customized branding.

You can update configurations, add or remove clients, and deactivate or delete clients as needed. Note that deactivating the SSO account won't affect the Verifier Account unless its advanced features are required.

Authorization API

After configuring your account and clients, you can set up the integration for your client service. The integration process is akin to that of Web 2.0 Identity Providers. You need to set the correct callback URLs, manage the attributes of the authorization flow, and handle the redirection of users with appropriate parameters to SSO.

This API is use-case agnostic and can be employed for various authorization processes, including user logins, KYC verifications, and authorizing financial transactions.