Skip to content

Conversation

@aaroncampbell
Copy link

  • Add password reset link for hosting.com
  • Add password reset link for a2hosting.com
  • Assert shared credentials from a2hosting.com to hosting.com

This is verified with personal knowledge as being Director of Product at A2Hosting and being significantly involved in our rebrand to hosting.com.

Overall Checklist

for change-password-URLs.json

  • There is no Well-Known URL for Changing Passwords (https://example.com/.well-known/change-password)
  • The URL either makes the experience better or no worse than being directed to just the domain in a non-logged-in state

for shared-credentials.json

  • 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.

* Add password reset link for hosting.com
* Add password reset link for a2hosting.com
* Assert shared credentials from a2hosting.com to hosting.com
@rmondello
Copy link
Contributor

The JSON in 'quirks/shared-credentials.json' isn't sorted!

Let’s fix that up and then we’ll be good to go.

@aaroncampbell
Copy link
Author

Just checking in to see if there's anything else needed from me here?

@jmulani jmulani self-requested a review July 8, 2025 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants