Expired proxy auth seems unnatural to recover from #722
Unanswered
SempleSituation
asked this question in
Q&A
Replies: 2 comments
-
|
Technically yeah that's what should happen. Your proxy should see the 401 response from Tinyauth and redirect you to the login screen. Can you please share your setup? Can't say much otherwise. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
It is incredibly possible I am doing this entirely wrong... I will try to set up a simple and shareable thing in the immediate future and update. Thanks for affirming my expectations. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey.
I am new to tinyauth and have set it up successfully and it works as expected. I have tried a few configurations and it is a major improvement over what it replaced. Thanks for it.
One issue I have outstanding involves when I have it configured at my proxy, and I am using the same ODIC provider in a workload (mealie is my current example). In this situation, when, what I assume is my proxies session expires, the mealie page produces a 401. Not a huge deal, except I would expect that refreshing would prompt for creds again.... and it does not. I have to manipulate the URL to go to the base and not whatever I was browsing, and then I can recover.
This is not a big deal for me... but I am hoping to expose this to others and my WAF will tank with any error.
Am I doing something wrong? I think my expectations would be that if I got a 401 by clicking, refreshing the page would re-auth me and make everything mo betta. Is this not how it should work?
Beta Was this translation helpful? Give feedback.
All reactions