Skip to content
Sudomimus

Manage sign-in methods

View as Markdown

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:

  1. Open Sign-in methods.
  2. Enter a name for the passkey, such as Work laptop or Security key.
  3. Choose Add passkey.
  4. Follow the browser’s passkey prompt on via.sudomimus.com.
  5. 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.

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 a link when its verified email would put the account under conflicting organization sign-in policies. Use a separate Sudomimus account or contact support if the organizations cannot align those policies.

Enroll email OTP

Section titled “Enroll email OTP”

Each verified email can have its own email-code sign-in method. In Verified emails, choose Enable email code login beside the address you want to use. Use an address you control and expect to keep receiving.

Email ownership and email-code sign-in are related but not identical: a verified email can be part of your profile without being enabled for sign-in.

You can also add another email and choose which verified address is primary. Before removing the primary email, set another verified address as primary. If an email is still used by a sign-in method, remove that method before removing the address.

Resolve an SSO authority conflict

Section titled “Resolve an SSO authority conflict”

The page shows a red warning when your verified emails belong to organizations that require different enterprise sign-in providers. While that warning is active, the account cannot start another sign-in or refresh access. Access that was already issued lasts only until its normal expiry.

Ask the relevant organization administrator or Sudomimus support to align the policies, remove a conflicting non-primary email, or separate the identities into different accounts. The warning disappears automatically once the conflict is resolved.

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.
Section titled “Related”