Replies: 3 comments 1 reply
-
Hello there ltomasik! 👋 Thank you and congratulations 🎉 for opening your very first issue in this project! 💖 In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀 |
Beta Was this translation helpful? Give feedback.
-
When I add parameters authorization-uri, token-uri, redirect-uri instead of issuer-uri application starts, but throws following error afterwards we tried to login through Azure AD . Probably my redirect-uri isn't correct. Should we define it as FQDN or localhost:8080
Error from application: 2023-05-01 10:40:20,647 WARN [reactor-http-epoll-1] r.n.h.c.HttpClientConnect: [766f87f8, L:/REDACTED-IP:58134 - R:login.microsoftonline.com/20.190.159.64:443] The connection observed an error |
Beta Was this translation helpful? Give feedback.
-
Hi, that's either a configuration issue or an issue with your provider. |
Beta Was this translation helpful? Give feedback.
-
Issue submitter TODO list
master
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
We want to configure Azure AD as oauth2 provider for Kafka-ui. Issuer uri value is loaded from config/environment variable, but isn't accepted by application and throwing following exception.
Expected behavior
Application should get all necessary information from issuer-uri endpoint: https://login.microsoftonline.com/REDACTED/v2.0/.well-known/openid-configuration
We also tried to run application with above mentioned issuer-uri endpoint, but got same exception
Your installation details
value: "OAUTH2"
value: "native"
value: "azuread"
value: REDACTED
value: REDACTED
value: "openid"
value: "https://login.microsoftonline.com/REDACTED/v2.0"
Steps to reproduce
execute helm install with oauth provider configuration
Screenshots
No response
Logs
Additional context
It seems to work when I remove issuer-uri and add authorization-uri, token-uri, redirect-uri to configuration.
Beta Was this translation helpful? Give feedback.
All reactions