You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We really need the ability to change cookie name, and that's why
To Reproduce
Steps to reproduce the behavior:
Create tinyauth.d1.com and so on, everything fine
Create another instance on another machine tinyauth.s1.d1.com and it looks fine but
Now we have (in browser) 2 cookies with arbitrary name tinyauth and distinguished Domain fields (.d1.com and .s1.d1.com)
Root (d1.com) works fine, but s1.d1.com can't login, after user/pass or oidc just redirects to login page and
tinyauth | 2025-05-19T22:11:44Z ERR Failed to get session error="securecookie: the value is not valid"
tinyauth | 2025-05-19T22:11:44Z ERR Failed to get session error="securecookie: the value is not valid"
tinyauth | 2025-05-19T22:11:44Z ERR Failed to get session cookie error="securecookie: the value is not valid"
Expected behavior
Just works
Additional context
Manual removing cookies helps till login to bothd1.com and s1.d1.com, then only first one works. I'm really not sure but suppose that problem should gone if cookie name will differ.
Never thought of this and that's indeed an issue. I will dynamically generate a cookie name based on either the domain or the secret. Basically a static unique identifier for the cookie. Will include it in the next release!
Activity
steveiliop56 commentedon May 20, 2025
Hello!
Never thought of this and that's indeed an issue. I will dynamically generate a cookie name based on either the domain or the secret. Basically a static unique identifier for the cookie. Will include it in the next release!
steveiliop56 commentedon May 25, 2025
Added in #161