Skip to main content

Hosted Auth pages

Hosted Auth pages are the user-facing screens Switera can show for sign-in, registration, recovery, verification, and device authorization. Review these pages before inviting real users so the flow feels consistent with your product.

Login page​

Hosted Switera login page
The login page should show only the sign-in methods you intentionally enabled for the app.

Test:

  • primary sign-in method
  • disabled or unavailable methods are not shown
  • wrong-password behavior
  • forgot-password link
  • post-login redirect
  • mobile layout

Registration page​

Hosted Switera registration page
Registration should match your launch model: open signup, invitation-only access, or controlled onboarding.

Before allowing public registration, confirm:

  • email verification policy
  • password policy
  • legal consent requirements
  • whether new users should be attached to an organization
  • what happens after successful registration

Recovery and verification​

Hosted Switera account recovery page
Recovery should send users to a mailbox and support path they recognize.
Hosted Switera email verification page
Verification protects the account flow before users access sensitive app areas.

Test recovery and verification with a test user before launch. Confirm email delivery, link expiry, error copy, and the destination after completion.

Device authorization​

Some CLI or device-style flows ask the user to enter a code in the browser.

Switera device authorization page with a sample code field
The user should already be signed in before approving a device or CLI authorization request.

For device flows:

  1. Start the CLI or device login flow.
  2. Open the URL shown by the tool.
  3. Sign in if needed.
  4. Enter or confirm the verification code.
  5. Authorize only devices you recognize.
  6. Return to the CLI or device and confirm it completed.

Before sharing hosted pages with customers:

  • review logo and app name
  • review primary color and button state
  • check terms and privacy links
  • confirm consent copy where required
  • test desktop and mobile widths
  • test every enabled provider

Redirect checks​

After a user completes a hosted page, confirm the destination is expected:

  • dashboard or app workspace for Builders
  • product callback for end users
  • invitation continuation for invited users
  • device completion for CLI/device authorization
  • recovery completion page for password reset

Unexpected redirects usually mean the return URL, callback URL, or flow continuation needs review.

Related pages: