Skip to content
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

v4: Additional cookie configurations #1889

Open
5 tasks done
mvvmm opened this issue Feb 7, 2025 · 1 comment
Open
5 tasks done

v4: Additional cookie configurations #1889

mvvmm opened this issue Feb 7, 2025 · 1 comment
Labels

Comments

@mvvmm
Copy link

mvvmm commented Feb 7, 2025

Checklist

  • I have looked into the Readme, Examples, and FAQ and have not found a suitable solution or answer.
  • I have looked into the API documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

This is kind of a piggy back off of #1853

In v3, we could configure all of:

AUTH0_COOKIE_DOMAIN
AUTH0_COOKIE_PATH
AUTH0_COOKIE_TRANSIENT
AUTH0_COOKIE_HTTP_ONLY
AUTH0_COOKIE_SECURE
AUTH0_COOKIE_SAME_SITE

via environment variables.

Looks like the work in #1872 only added support for configuring name, secure, and sameSite. I know my team also configures the domain and transient properties.

Describe the ideal solution

Add support for all the existing cookie configurations in v3 to also be configured in v4.

Alternatives and current workarounds

None, that I'm aware of

Additional context

This is important for sharing sessions between same domain applications.

We have app1 and app2 that want to share sessions between them, so we configure the cookie_domain to be .ourdomain.com instead of app1.ourdomain.com or app2.ourdomain.com.

@tusharpandey13
Copy link
Contributor

Thank you for reporting this, we are actively looking into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants