Allow custom domains to use alternative origins #2399
Merged
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.
This PR lifts the restriction on the alternative origins feature to only allow canister id based subdomains of
ic0.app
andicp0.io
.The canister id resolution is now the same for the session authorization flow as it is for verifiable credentials.
The following restriction is still in place: the alternative origins file needs to be served from a canister accessible on the
icp0.io
domain.Allowances are made for local development using
localhost
,0.0.0.0
,127.0.0.1
and custom HTTP gateways.This PR also adds a unit test suite for the derivation origin validation.
🟡 Some screens were changed