Configurer l'authentification JWT sur le backend super-grah #7
Labels
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#8 Authentification JWT sur le backend super-graph
Cadoles/daddy
You do not have permission to read 1 dependency
Reference: Cadoles/daddy#7
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
L'authentification OpenID Connect étant implémentée via la PR #6, il faut désormais configurer le backend super-graph de l'infrastructure Docker afin qu'il authentifie les requêtes à partir du jeton JWT qui sera transmis dans les requêtes sur l'API GraphQL (via une entête
Authorization: Bearer <access_token>
.Informations utiles
access_token
est persisté dans lelocalStorage
via la fonctionsaveAccessGrant()
dans le fichierfrontend/src/util/auth.ts
. La méthodegetSavedAccessGrant()
permet de récupérer celui ci.super-graph
pour l'utilisatation des JWTsdocker-compose.yml
)wpetit referenced this issue2020-06-21 11:32:23 +02:00
wpetit referenced this issue2020-06-21 14:28:54 +02:00
wpetit referenced this issue2020-06-21 14:31:24 +02:00
wpetit referenced this issue2020-06-21 14:31:44 +02:00
wpetit referenced this issue2020-06-21 14:34:15 +02:00
wpetit referenced this issue2020-06-21 14:35:07 +02:00
Le backend super-graph a été mis de côté au profit d'un backend GraphQL Go classique.