Hi Everyone
This is an announcement for an upcoming proposal (hopefully later today) to upgrade Internet Identity to a new release.
This new release will contain one notable new feature, which is the ability for dapp developers to move the front-end origin to a new domain, while keeping the principals of the users stable. The corresponding specification changes were merged last week in this PR: Add specification for canister chosen alternative domains by frederikrothenberger · Pull Request #724 · dfinity/internet-identity · GitHub
For users, authenticating for a dapp using this feature will look like this (subject to change):
Note: Once released, this feature will be in an experimental phase until marked stable. While you are free to start using it right from the start, there might still be some protocol changes in the coming weeks. The current plan is to stabilize this feature by end of July.
Please let us know, what you think.
22 Likes
The proposal has been submitted: Internet Computer Network Status
2 Likes
The proposal has now been passed and the feature is available on https://identity.ic0.app
6 Likes
We are using Icfront to redirect requests now, anything needs to change to use it?
the short of it is - if you add a json-encoded array of strings at /.well-known/ii-alternative-origins for the domains you’re redirecting from, you can instead host the serviceworker at the custom domain, and then pass a derivationOrigin during authClient.login, specifying the canister id url that you have been redirecting to.
Full tutorial to come, plus there will be official support in the next releases of agent-js and dfx
10 Likes
Awesome news! One thing we really needed.
Really amazing to see this. On the right direction…
kinwo
August 16, 2022, 5:00am
8
Does anyone try this on origin with asset type canister? Since /.well-known/ii-alternative-origins is in hidden directory, dfx deploy doesn’t add it to the deploy list.
Any suggestions?
I think this is supported in dfx 0.11.0 0.11.1 via .ic-assets.json: sdk/CHANGELOG.md at master · dfinity/sdk · GitHub
These examples might help:
dfinity:main ← dfinity:SDK-592-configurable-hidden-directories-files-inclusion-when-uploading-assets
opened 05:22PM - 12 Jul 22 UTC
# Description
Closes https://dfinity.atlassian.net/browse/SDK-592.
#### incl… ude all hidden files
```json
[
{ "match": ".*", "ignore": false }
]
```
#### include all non-dotfiles from `.well-known` directory
```json
[
{ "match": ".well-known", "ignore": false }
]
```
#### include all non-dotfiles from `.well-known` directory + a specific dotfile from that dir
`/.ic-assets.json`
```json
[
{ "match": ".well-known", "ignore": false }
]
```
`/.well-known/.ic-assets.json`
```json
[
{ "match": ".dotfile", "ignore": false }
]
```
# How Has This Been Tested?
Unit tested `sync::gather_asset_descriptors`, see: https://github.com/dfinity/agent-rs/blob/f8515d1d0825b47c8048f5528ac3b65018065779/ic-asset/src/sync.rs#L145
# Checklist:
- [x] The title of this PR complies with [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
- [x] I have edited the CHANGELOG accordingly.
- [ ] I have made corresponding changes to the documentation.
1 Like
mnl
August 16, 2022, 11:13am
10
Paul pointed you to the best resources available, however, please note the feature is available since 0.11.1 (not 0.11.0).
Let me know if you’ll need more help
3 Likes
kinwo
August 17, 2022, 12:58am
11
Thanks a lot! It works. You saved my day.
1 Like
It’s so confuse for me, can anyone give more details of how to use it?
1 Like
