Identity | Add instructions on developing with okta/sign in local dev #27791
+28
−16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
For Frontend local development we want to be able to use Okta/OAuth tokens locally during development to test and develop against signed in features.
This is currently very difficult as Frontend developments happens on localhost, which cannot share cookies with Identity/Okta, which runs on https on the
profile
subdomain.However Fronend can be run on
https://m.thegulocal.com
by following these instructions. Since that does run locally using https, and on thethegulocal.com
domain, it makes it possible to share cookies with Okta.This PR updates those instructions with updated ones showing exactly the steps needed to be taken in order to enable this. It also updates
@guardian/identity-auth-frontend
which enables the use of this domain in local development (see the CSNX and Identity Platform PRs below).Related PRs
Identity Platform: https://github.com/guardian/identity-platform/pull/802
Dotcom Rendering: guardian/dotcom-rendering#13426
CSNX: guardian/csnx#1964
Frontend (This PR): #27791
Tested