Community Documentation
Client Credentials Authorization
Document updated on Nov 23, 2021
About this feature
| Namespace | auth/client-credentials |
|---|---|
| Scope | backend |
| Source | krakend/krakend-oauth2-clientcredentials |
Through the OAuth 2.0 Client Credentials Grant, KrakenD can do a 2-legged OAuth2 flow, which means that the gateway requests to your authorization server an access token before reaching the backend’s protected resources. This token is passed in the “Authorization” header. The token refreshes when needed.
The client credentials authorize KrakenD, as the client, to access the protected resources.
Successfully setting the client credentials for a backend means that KrakenD can get the protected content. Still, the endpoint offered to the end-user will be public unless you protect it with JWT or another end-user authentication mechanism.
Configuring OAuth2 Client Credentials
To access a protected resource using client-credentials, add under every backend the appropriate extra_config.
The namespace used is "auth/client-credentials". Sample configuration below:
{
"backend": [
{
"url_pattern": "/protected-resource",
"extra_config": {
"auth/client-credentials": {
"client_id": "YOUR-CLIENT-ID",
"client_secret": "YOUR-CLIENT-SECRET",
"token_url": "https://your.custom.identity.service.tld/token_endpoint",
"endpoint_params": {
"audience": ["YOUR-AUDIENCE"]
}
}
}
}
]
}
The settings of this component are:
Fields of OAuth2 client-credentials
| The Client ID provided to the Auth server |
| The secret string provided to the Auth server. Example: "mys3cr3t" |
| Any additional parameters you want to include in the payload when requesting the token. For instance, adding the audience request parameter may denote the target API for which the token should be issued.Example: {"audience":["YOUR-AUDIENCE"]} |
| A comma-separated list of scopes needed, e.g.: scopeA,scopeBExample: "scopeA,scopeB" |
| The endpoint URL where the negotiation of the token happens Example: "https://your.custom.identity.service.tld/token_endpoint" |
Auth0 integration
The following example demonstrates a complete configuration to fulfill the requirements of Auth0. It is essentially the same configuration we have shown above, but with some additions, explained after the code:
{
"endpoint": "/endpoint",
"backend": [{
"url_pattern": "/backend",
"extra_config": {
"auth/client-credentials": {
"client_id": "YOUR-CLIENT-ID",
"client_secret": "YOUR-CLIENT-SECRET",
"token_url": "https://custom.auth0.tld/token_endpoint",
"endpoint_params": {
"client_id": ["YOUR-CLIENT-ID"],
"client_secret": ["YOUR-CLIENT-SECRET"],
"audience": ["YOUR-AUDIENCE"]
}
},
"modifier/martian": {
"fifo.Group": {
"scope": ["request", "response"],
"aggregateErrors": false,
"modifiers": [
{
"header.Modifier": {
"scope": ["request"],
"name" : "Accept",
"value" : "application/json"
}
}
]
}
}
}
}]
}
The code above works with Auth0. The difference with the basic example is the way both the id and the secret are passed as endpoint_params, as auth0 ignores the auth header and expects the credentials sent as JSON data or form body.
