|
Hey, I'm adopting this plugin in my organization, but I notice that, when I add the plugin, every navigation inside of It forces a Login. Example: Main Qeta page -> Navigate to New Question page -> Login page Opens |
Answered by
drodil
Feb 4, 2023
Replies: 1 comment 1 reply
|
Hi. Thanks for the report. I am not sure what could cause this. We are also using this plugin in our organization, and it's also behind authentication, without any problems. What authentication provider are you using? I could try to reproduce this with that. And have you tried using configuration value qeta.allowAnonymous=true? The user is fetched using identityApi and if it cannot get user's name, it will return HTTP 401 unauthorized which may cause redirection to login page. |
1 reply
Answer selected by
leonarhv
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi. Thanks for the report. I am not sure what could cause this. We are also using this plugin in our organization, and it's also behind authentication, without any problems. What authentication provider are you using? I could try to reproduce this with that. And have you tried using configuration value qeta.allowAnonymous=true? The user is fetched using identityApi and if it cannot get user's name, it will return HTTP 401 unauthorized which may cause redirection to login page.