For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

For the complete documentation index, see llms.txt

Signicat OIDC SDK

The Signicat OIDC SDK authenticates end-users in your app with your Signicat OIDC client, which you configure in the Signicat Dashboard.

How does the SDK work?​

The SDK provides an API built on AppAuth for integrating with the Signicat OIDC service.

The SDK implements the Authorisation Code Flow. Its configuration has the following characteristics:

  • The redirect URI is an HTTPS link.
  • The client operates as a public client using Proof Key for Code Exchange (PKCE), which removes the need for a client secret.
  • The configuration interface maps directly to the OIDC specification. For example, you can pass acr_values to filter the identity methods shown to the end-user.

Where authorisation takes place depends on the platform:

Want to learn more?

To learn more about these best practices, see our OIDC Native mobile apps page.

What does the SDK handle?​

The SDK automatically manages the following processes:

  • OIDC discovery.
  • Authorisation with PKCE.
  • Redirect handling and authorisation code exchange.
  • Access token refresh.
  • Requests to the UserInfo endpoint.
  • Logout at the Signicat service's end-session endpoint.
  • Optional session persistence between app launches.

Choose your platform​

Choose your platform to start integrating the SDK into your app: