{"repo":"AxisCommunications/go-dpop","free":true,"listed":false,"github":"https://github.com/AxisCommunications/go-dpop","clone":"git clone https://github.com/AxisCommunications/go-dpop.git","description":"DPoP for golang clients and servers","language":"Go","stars":16,"topics":["dpop","golang-library","oauth2"],"license":"MIT","category":"auth-billing-email","readme_excerpt":"go-dpop OAuth 2.0 Demonstrating Proof of Possession (DPoP) This package tries to implement RFC-9449 Supported key algorithms Supported: - ES256, ES384, ES521 - RS256, PS256 - Ed25519 How to use Authorization server An authorization server needs to parse the incoming proof in order to associate the public key of the proof with the bound access token. It should parse the proof to ensure that the sender of the proof has access to the private key. Resource server Resource servers need to do the same proof validation that authorization servers do but also check that the proof and access token are bound correctly. Client A client can generate proofs that authorization and resource servers can validate. Note on HMAC Although this package can in theory support symmetric keys the DPoP draft does not allow private keys to be sent in the proof jwk header. As a symmetric key has no public key cryptography it can not be included in the proof, hence why it is unsupported.","default_branch":null,"files":null,"tree":[],"storefront":"/r/AxisCommunications","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/AxisCommunications/go-dpop/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}