HTX Login — fast, secure sign-in and recovery
Short guide: what to expect and how to solve common problems
The HTX login is the doorway to apps, classroom portals and developer tools. This page explains the sign-in flow, how to set up multi-factor authentication (MFA), how to recover access, and how to keep sessions safe across devices. The steps below apply whether you’re a student, faculty, or a technical user integrating single sign-on (SSO).
How HTX login works (quick overview)
HTX uses an identity service that supports username/password plus optional SSO through institutional identity providers (SAML, OIDC) and handles session tokens for web and mobile clients. Sign-in creates a short-lived session token and — if enabled — an MFA challenge. The login page you see may change slightly depending on whether you arrive from a campus portal, an external app, or an API request.
Step-by-step: signing in
- Open the official HTX sign-in page or the link provided by your department.
- Enter your HTX identifier (usually your institutional email) in the username field.
- Type your password carefully; paste only from a trusted password manager to avoid clipboard leaks.
- If your account requires MFA, complete the second factor (TOTP code, push approval, or security key).
- Choose "Remember this device" only on private, secure devices — corporate-managed machines already have controls.
Multi-factor and device safety
Enabling MFA reduces credential theft drastically. HTX supports one-time codes (TOTP apps like Authenticator), security keys (FIDO2) and push-based authenticators. Register at least two second-factor methods to avoid lockout: one phone app and an emergency backup code stored safely offline.
Common problems & immediate fixes
- Forgot password: Use the “Forgot password” flow on the sign-in page. Verify from your recovery email or phone.
- MFA device lost: Use recovery codes, or contact HTX support for an identity re-check. Expect an identity verification step.
- Broken SSO redirect: Clear cookies for the HTX domain and retry; SSO flows are sensitive to stale session cookies.
- Session expires too quickly: Confirm whether your browser or a privacy extension blocks persistent cookies. HTX relies on secure cookies and local storage for session state.
Integrators: SSO & developer notes
When integrating HTX via OIDC/SAML, use strict audience and redirect validation. Don’t embed credentials in client-side code. Use short access tokens and refresh token rotation. When possible, prefer server-side exchange for sensitive tokens and enable strict CORS policies.