Authorisation

OneBasket comes out of the box with an OIDC compliant authorisation mechanism, based on the present of a JWT bearer token in the header of the request.

Each OneBasket store is configured with a single OIDC provider before going live.

The sub claim in the JWT (known as the "Auth Provider User Id") is then used to map authenticated requests to a known OneBasket user.