providers/oauth2: allow m2m for JWKS without alg in keys (#12196)

* providers/oauth2: allow m2m for JWKS without alg in keys

Signed-off-by: Jens Langhammer <jens@goauthentik.io>

* Update index.md

Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
Signed-off-by: Jens L. <jens@beryju.org>

* Apply suggestions from code review

Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
Signed-off-by: Jens L. <jens@beryju.org>

---------

Signed-off-by: Jens Langhammer <jens@goauthentik.io>
Signed-off-by: Jens L. <jens@beryju.org>
Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
This commit is contained in:
Jens L.
2024-11-27 19:01:40 +01:00
committed by GitHub
parent c05124c9dd
commit f9e8138be3
5 changed files with 28 additions and 6 deletions

View File

@ -14,7 +14,7 @@ authentik doesn't ship with a default flow for this usecase, so it is recommende
The flow is initiated by sending a POST request to the device authorization endpoint, `/application/o/device/` with the following contents:
```
```http
POST /application/o/device/ HTTP/1.1
Host: authentik.company
Content-Type: application/x-www-form-urlencoded
@ -36,7 +36,7 @@ The response contains the following fields:
With this response, the device can start checking the status of the token by sending requests to the token endpoint like this:
```
```http
POST /application/o/token/ HTTP/1.1
Host: authentik.company
Content-Type: application/x-www-form-urlencoded