Login marketing cookie
What does this MR do and why?
Describe in detail what your merge request does and why.
We would like to create a first party cookie in the product that will enable the marketing site to recognize a logged in Gitlab user.
Engineering Notes
The user's session ID can be stored in a cookie on the client-side, and sent with each request to the server. The server can then look up the user's session in the database(or API) to determine if they are logged in or not.
This solution was also suggested by a Staff Support Engineer in the #g_manage_auth slack channel
related to: gitlab-com/marketing/digital-experience/buyer-experience#1919 (closed)
Screenshots or screen recordings
How to set up and validate locally
- Spin up GDK locally
- Open Devtools > Application > Cookies
- login cookie's value will change from true to false when user logins in and out
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Miracle Banks