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
You may want local identity cookies to be available in `dotcom-rendering`. To enable this:
65
+
You may want to develop against signed in behaviour in `dotcom-rendering`.
66
+
In order for this to work you have to run `dotcom-rendering` on a local domain with `https`.
66
67
67
-
1. run `./scripts/nginx/setup.sh`
68
-
1. access `dotcom-rendering` through https://r.thegulocal.com
68
+
To set this up this:
69
+
70
+
1. Run `./scripts/nginx/setup.sh`
71
+
72
+
- This will create a local domain `r.thegulocal.com` and set up a reverse proxy to `localhost:3030` with a valid SSL certificate.
73
+
74
+
2.`dotcom-rendering` can now be accessed through https://r.thegulocal.com when running the development server
75
+
3. Sign in to https://profile.code.dev-theguardian.com/ on a separate tab/window
76
+
77
+
- Third party cookies must be enabled in your browser for this to work
78
+
79
+
4. Back on `dotcom-rendering` under https://r.thegulocal.com set a cookie with the name `GU_U` with any value on the `r.thegulocal.com` domain and refresh the page
80
+
5. You should now be signed in!
81
+
82
+
- You should see the header change to show `My Account` instead of `Sign in`
83
+
- In local storage you should see a key `gu.access_token` and `gu.id_token` with the values of the tokens you are signed in with
0 commit comments