-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forward cookies from request #1804
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain a bit more about how youre using this specifically? When are the authelia headers getting set initially?
So I have a bunch of services on a subdomain, all behind authelia. Requests made to The idea here is that when a request comes in to homepage, we take the cookies from the cookie header, add them to the cookie jar, and then they can be used in requests to the actual services. |
I still havent tested this out much, but it looks OK to me. Any reason its still a draft? |
@j-waters if youre still interested in this let us know, otherwise we'll close it out |
Sorry yeah I'm still interested, been using this branch in my home setup for about a month now and haven't found any issues |
I'd like to add this to the docs somewhere, not sure where. Hmm... |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns. |
Proposed change
Take any cookies that are present on the request to endpoints such as
api/ping
andapi/services
and add them to the cookie jar. This means that services that are behind authentication such as authelia can be pinged and used in widgets.The way this is done probably isn't overly correct - but it works for my usage. I thought I'd make an MR anyway to see if there was any interest in this feature.
Closes #1797
Type of change
Checklist:
pnpm lint
.