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 user securely fulfills such requirements before permitting access and allows users to consent to explicitly sharing personal data with you. Users experience a smooth 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 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. Configure the Connect URLs Feature within your developer application. This will help you define the necessary components to use the GlobaliD Connect feature to work with users to connect to your service with a username + password ("Web Connect") or the GlobaliD app + a QR code ("App Connect"). Both App Connect and Web Connect are jointly referred to as 'Connect.'

    • Using Connect, users will be able login/signup, and partner applications can authorize users via standard Oauth 2.0 principles. Visit this page to learn how to generate an instance of GlobaliD Connect.
  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 App Connect or Web Connect 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. 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.