[x] There's evidence the domains are currently related (SSL certificates, DNS entries, valid links between sites, legal documents etc.)
[ ] If using 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 a shared association from google.co.il to google.com, because google.co.il redirects to accounts.google.com for sign in.)
[ ] If using from and to, the new group, the from domain(s) redirect to the to domain to log in.
talent.seek.com.au is now using authenticate.seek.com for authentication, it previously used authenticate.seek.com.au.
The old domain does not redirect to the new domain, as it is now obsolete and no longer linked to. But you can see that this assetlinks file has a similar association to the one suggested in this PR https://authenticate.seek.com/.well-known/assetlinks.json
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 asharedassociation fromgoogle.co.iltogoogle.com, becausegoogle.co.ilredirects toaccounts.google.comfor sign in.)fromandto, the new group, thefromdomain(s) redirect to thetodomain to log in.talent.seek.com.auis now usingauthenticate.seek.comfor authentication, it previously usedauthenticate.seek.com.au. The old domain does not redirect to the new domain, as it is now obsolete and no longer linked to. But you can see that this assetlinks file has a similar association to the one suggested in this PR https://authenticate.seek.com/.well-known/assetlinks.json