Manage sign-in methods
Sign-in methods are the ways your Sudomimus account can prove it is you. One account can have several methods: passkeys, email OTP, Google, GitHub, Discord, Battle.net, X, Steam, and enterprise federation.
Open with.sudomimus.com, then go to Account → Sign-in methods.
Add a passkey
Section titled “Add a passkey”Passkeys must be created on via.sudomimus.com, because browsers bind passkeys to a relying-party domain.
From the With portal:
- Open Sign-in methods.
- Enter a name for the passkey, such as
Work laptoporSecurity key. - Choose Add passkey.
- Follow the browser’s passkey prompt on
via.sudomimus.com. - Return to the With portal and confirm the success message.
You can add more than one passkey. Use names that help you recognize the device later.
Link a provider
Section titled “Link a provider”Provider linking starts in the With portal and finishes on via.sudomimus.com or the upstream provider.
Use this when you want the same account to accept another provider, such as Google or GitHub. If the provider account is already linked elsewhere, the portal will stop the link instead of silently moving it.
Sudomimus also stops an OAuth or Steam link when its verified email would make
the account subject to different SSO_ONLY connectors. Choosing either IdP
would bypass the other domain owner’s policy, so the link is not written.
Enroll email OTP
Section titled “Enroll email OTP”If your account does not already have email OTP as a sign-in method, you can add it from the sign-in methods page. Use an email address you control and can continue receiving.
Email ownership and email OTP are related but not identical: a verified email can be part of your profile, and email OTP is one way to sign in.
Resolve an SSO authority conflict
Section titled “Resolve an SSO authority conflict”The page shows a red warning when your current verified emails belong to domains that require different SSO connectors. While that warning is active, the account cannot start another login or receive fresh tokens; an access token that was already issued remains valid only until its normal expiry.
Ask the relevant domain administrator or Sudomimus staff to align a domain policy, remove a conflicting verified email, or separate the identities into different accounts. The warning disappears automatically once the live domain and email ownership state is no longer conflicting.
Remove a sign-in method
Section titled “Remove a sign-in method”Remove credentials you no longer control, such as an old passkey or a provider account you no longer use.
Before removing a method:
- Make sure at least one other sign-in method remains.
- Avoid removing the only method you can use on your current device.
- Remove lost or shared-device passkeys promptly.
Related
Section titled “Related”- Accounts and credentials - how accounts, emails, and authentication methods relate.
- Layer 1 — Authentication rules - which sign-in methods an application can allow.