Closed JulienParis86 closed 2 years ago
Hi,
Since you have added the "login" subdomain variants for the three domains to shared-credentials.json
, you should remove the domains from shared-credentials-historical.json
.
You will also need to update websites-with-shared-credential-backends.json
by running tools/convert-shared-credential-to-legacy-format.rb.
About the failed CI job: The shared-credentials.json
should be sorted alphabetically. Currently, domains starting with the letter L (login...
) are grouped with domains starting with the letter A.
Thanks @Sameesunkaria for your help understanding my mistake :)
For record keeping purposes:
At the time of this comment, the login.airfrance.com
and login.klm.com
map to the same CNAME record and all three domains resolve to the same IP addresses:
login.airfrance.com canonical name = login.airfrance.com.edgekey.net.
login.airfrance.com.edgekey.net canonical name = e77721.a.akamaiedge.net.
Name: e77721.a.akamaiedge.net
Address: 88.221.221.168
Name: e77721.a.akamaiedge.net
Address: 88.221.221.146
login.klm.com canonical name = login.klm.com.edgekey.net.
login.klm.com.edgekey.net canonical name = e77721.a.akamaiedge.net.
Name: e77721.a.akamaiedge.net
Address: 88.221.221.168
Name: e77721.a.akamaiedge.net
Address: 88.221.221.146
login.flyingblue.com canonical name = login.flyingblue.com.edgekey.net.
login.flyingblue.com.edgekey.net canonical name = e77721.dsca.akamaiedge.net.
Name: e77721.dsca.akamaiedge.net
Address: 88.221.221.168
Name: e77721.dsca.akamaiedge.net
Address: 88.221.221.146
Thank you @JulienParis86 The changes look good to me :)
Screenshots of the pages:
Overall Checklist
for shared-credentials.json
shared
, the new group serves login pages on each of the included domains, and those login pages accept accounts from the others. (For example, we wouldn't use ashared
association fromgoogle.co.il
togoogle.com
, becausegoogle.co.il
redirects toaccounts.google.com
for sign in.)from
andto
, the new group, thefrom
domain(s) redirect to theto
domain to log in.