Expand description
GNAP (Grant Negotiation and Authorization Protocol) implementation.
This module implements the GNAP specification (draft-ietf-gnap-core-protocol), providing an emerging next-generation alternative to OAuth 2.0 with stronger cryptographic binding and a unified request structure.
§Implemented Features
- Transaction lifecycle (create, continue, approve, deny)
- Client key binding via JWK (ES256, RS256, EdDSA); a client key is required
- Access granted only through a
GnapAccessPolicy(default deny) - One-time interaction reference and hash (draft §4.2, §4.2.3)
- Continuation token rotation on each use
- Token management (revocation)
- Subject information responses
- Transaction expiration and cleanup
Structs§
- Gnap
Access Request - Description of a single access right being requested
- Gnap
Client Display - Gnap
Client Info - Gnap
Client Key - Client key with proof method (draft §7.1)
- Gnap
Config - Gnap
Interaction Completion - What the authorization server hands back to the client when the resource owner approves a
transaction that uses an interaction
finishmethod (RFC 9635 section 4.2). - Gnap
Interaction Finish - Gnap
Interaction Requirements - GnapJwk
- Minimal JWK representation sufficient for GNAP key binding
- Gnap
Proof - The HTTP request a client key signs, handed to the
_with_proofentry points. - Gnap
Service - Gnap
Subject Request - Subject information the client is requesting
- Gnap
Transaction Request - A GNAP transaction request representing the client’s intent
- Gnap
Transaction Request Builder - Builder for
GnapTransactionRequest.
Traits§
- Gnap
Access Policy - Decides which access rights a client key is granted.