-
Notifications
You must be signed in to change notification settings - Fork 46
Support Header Authenication #91
Comments
Sorry, I don't quite understand what the app should do here. Should it open a website with your authentication page and acquire a cookie for API access? |
Yes I think that would be best course of action. |
Thank you, that makes it a bit clearer. Still, I'm missing some information required to implement this:
|
I think it is pretty common practice to use a reverse proxy with an x.509 certificate. If the app supported that, it would be great! |
I'm using a secure access gateway in front of my paperless instance as well. |
Ill get on this band wagon for 2fa support for signon also. Currently using the iOS version. |
Is your feature request related to a problem? Please describe.
Logging into the app.
Describe the solution you'd like
Supporting reverse proxy fronted header authentication.
Additional context
My paperless instance is fronted by a authorization proxy that passes headers for authorization to paperless. For example reaching my instance would forward you to login then redirect you back to paperless providing paperless with it's username header.
Not sure if it's even possible but it would be great if the app can support this kind of login flow.
The text was updated successfully, but these errors were encountered: