G2P Connect
  • G2P Connect
    • 🔍Overview
    • 📘Solution Blueprint
  • Protocol
    • 🔍Overview
    • 🔡Terminology
    • 🔗Interfaces
      • Identity
      • Credentialing
      • Registries
        • Social Registry
      • Beneficiary Management
        • Mapper Architecture
        • Mapper Specs
        • Eligibility Determination
      • Program Management
        • Disbursement
    • 🔐Security
      • Authorization
      • Singature Validation
  • Additional Info
    • 🤼Discussions
    • 👉References
    • 🙏Acknowledgments
    • 🤝Licensing
  • Group 1
Powered by GitBook

Content of this site is licensed under CC BY-SA 4.0 by CDPI

On this page
  • Overview
  • Interface List
  • Integration Schematics

Was this helpful?

  1. Protocol
  2. Security

Authorization

PreviousSecurityNextSingature Validation

Last updated 1 year ago

Was this helpful?

Overview

  1. The scope of these end points is to standardise issuance of access tokens using existing OAuth2/OIDC standards.\

  2. Helps standardise end point access across g2p complaint api stack using x-access-token that is compliant with JWT specs.\

  3. DPGs & COTS products may also provide similar authz api end points with G2P Connect documented scopes as part of each country specific implementation (if any).\

  4. Additional security like IP white listing, private networks, etc are outside the scope of G2P Connect standards. Each country shall decide required operational models.\

References

  1. API specification

  2. Discussion

Interface List

Interface ID
End Point
Description

AUTHZ-TOKN

/oauth2/client/token

Provide access token to registered senders & receivers

Integration Schematics

🔐
link
thread