The Authorization API

The Authorization Endpoint provides a protocol that mediates authorization between your application and a user’s authenticated identity. It ensures that the a user fulfills such requirements before permitting access, allows users to consent explicitly sharing personal data with you, and securely communicates requirements for access to users. Users experience a smooth, near-instant onboarding/ login process by scanning a QR code, tapping a button on mobile, or logging in via a username/password.

This provides a lightweight solution with heavyweight benefits, including: - A secure and seamless authentication experience to login and signup users

  • Certainty that all authorized users have verified the partner-specified credentials throug the required verifications feature
  • In very few cases dealing with legal compliance and explicit user consent, access to underlying personable and identifiable information (PII) stored in a secure vault
  • All in all, a complete identity stack solution that allows you to focus on building your product rather than data collection, compliance, and security

How it Works and Setup

Authorization API Diagram

After setting up a developer account, partners will complete the following steps to enable and get started with authorization workflows:

  1. Instantiate a globaliD Connect feature and define a redirect URL, or integrate theWeb Client to route users to globaliD

    • Here, users will be able login/signup, and partner applications will receive an authentication token in return
  2. If a service requires certain verifications from your users, instantiate at least one Required Verification feature

    • Partner applications can define a set of requirements users must verify about their identity. Users will be asked to verify they meet these requirements through the use of globaliD connect or the globaliD web client.

    • As an example, you may require that your users verify their government ID before they can use your banking service, or verify they are above a certain age before purchasing goods on your site.

  3. Integrate globalid Connect or the Web Client into you project

    • Upon completion, users will be redirected to a URL defined by partners in the globaliD Connect Feature. The partner application will either receive an authorization code or an auth token in returned depending on the depending on the specified scope.
  4. In some cases, globaliD will allow partners to enable PII Sharing as a feature to access underlying private user information should the application require it for compliance purposes or to contact users.