Timeline for Achieving Multitenancy with an External Identity Provider
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 16 at 18:12 | history | edited | Ewan | CC BY-SA 4.0 | deleted 10 characters in body |
| Sep 16 at 16:37 | comment | added | JimmyJames | JWTs are encoded, not encrypted. | |
| Sep 6 at 19:27 | comment | added | ikiwq | If token exchanging is a good option, then at which level should it be performed? Should it be performed by the frontend application when the user switches between organisations? Or should it by an API Gateway, by intercepting the request and injecting the new token? | |
| Sep 5 at 11:30 | history | edited | Ewan | CC BY-SA 4.0 | added 188 characters in body |
| Sep 5 at 11:27 | comment | added | Ewan | I think that would be the base approach yes. A different jwt passed depending on the users selected tenant. Obvs you don't want to force multiple logins, but I don't see that as something that cant be solved. | |
| Sep 5 at 9:29 | comment | added | Basilevs | When user is signed in into multiple organizations, do you suggest to exchange multiple JWT tokens? | |
| Sep 5 at 9:05 | history | answered | Ewan | CC BY-SA 4.0 |