Consumer Authentication and Multi-Factor Authentication

Authentication Method

myTraderDash uses OpenID Connect (OIDC) for all user authentication. The application does not implement its own credential storage or password-based login. All authentication is delegated to trusted identity providers.

Supported Identity Providers

Google — OpenID Connect with PKCE.

Apple (Sign in with Apple) — OpenID Connect with PKCE.

Yahoo — OpenID Connect with PKCE.

Sign-in requires an email address that the identity provider reports as verified.

Multi-Factor Authentication

MFA is available to all users through their chosen identity provider. Google, Apple, and Yahoo all support two-step verification, including methods such as authenticator apps, trusted devices, security keys, or SMS. Since authentication is fully delegated to OIDC providers, MFA enforcement is controlled at the provider level.

Authentication Flow

1. User clicks "Sign in with Google", "Sign in with Apple", or "Sign in with Yahoo".

2. User is redirected to the provider's authentication page.

3. Provider handles credential verification and MFA challenge.

4. On success, provider returns an ID token.

5. myTraderDash creates a session (Redis-backed store, referenced by an HttpOnly cookie).

6. Session is bound to the user's workspace.

Session Security

Sessions stored in Redis and expire after 30 days of inactivity.

HttpOnly, Secure, SameSite cookies.

Sessions invalidated on logout and on account deletion.

PKCE prevents authorization code interception.

Sign-in endpoints are rate limited.

Access to Financial Data

Brokerage and financial account connection flows (such as SnapTrade and Plaid) are only accessible to authenticated users. A valid session is required before any connection flow can be initiated, and the provider's own consent screens provide additional authorization.

Contact

General — admin@mytraderdash.com

Support — support@mytraderdash.com

Privacy — privacy@mytraderdash.com

Security — security@mytraderdash.com