| Draft7 | validator.json | JWT validator | Protect endpoints from public usage by validating JWT tokens generated by any industry-standard OpenID Connect (OIDC) integration.
See: https://www.krakend.io/docs/authorization/jwt-validation/ |
| Draft7 | signer.json | JWT signer | creates a wrapper for your login endpoint that signs with your secret key the selected fields of the backend payload right before returning the content to the end-user.
See: https://www.krakend.io/docs/authorization/jwt-signing/ |
| Draft7 | revoker.json | Revoke Server | The API Gateway authorizes users that provide valid tokens according to your criteria, but at some point, you might want to change your mind and decide to revoke JWT tokens that are still valid. |
| Draft7 | client-credentials.json | OAuth2 client-credentials | 2-legged OAuth2 flow: Request to your authorization server an access token to reach protected resources.
See: https://www.krakend.io/docs/authorization/client-credentials/ |
| Draft7 | basic.json | - | Enterprise only. The Basic Authentication component protects the access to selected endpoints using basic username and password credentials.
See: https://www.krakend.io/docs/enterprise/authentication/basic-authentication/ |
| Draft7 | api-keys.json | API-key Authentication | Enterprise only. Enables a Role-Based Access Control (RBAC) mechanism by reading the `Authorization` header of incoming requests.
See: https://www.krakend.io/docs/enterprise/authentication/api-keys/ |