Integration of Luigi with authentication provider that does not have PKCE enabled #2643
-
We are integrating Luigi with an authentication provider that does not have PKCE enabled and mandates the client secret to be passed for retrieving a token. It’s not secure to keep |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Luigi’s authentication provider mechanism is intended to support developers in integrating "standard" client-side-flow authentication providers, like OIDC. If your scenario requires a custom backend implementation, I would rather recommend not to use it since it would add unnecessary complexity. The good thing is that Luigi also works perfectly fine without it, and you can easily secure your application as any other "conventional" application (i.e. on server side with some session cookie based approach). Here is a small example of how it can look like:
|
Beta Was this translation helpful? Give feedback.
Luigi’s authentication provider mechanism is intended to support developers in integrating "standard" client-side-flow authentication providers, like OIDC. If your scenario requires a custom backend implementation, I would rather recommend not to use it since it would add unnecessary complexity. The good thing is that Luigi also works perfectly fine without it, and you can easily secure your application as any other "conventional" application (i.e. on server side with some session cookie based approach).
Here is a small example of how it can look like: