ProtectedconfigProtectedisReadonlytypeProvider type identifier Must be implemented by concrete providers
ProtecteduserProtecteduserStatic ReadonlyPROVIDER_Contains the initial path from window.location.pathname before any work was done by auth services
Contains the initial search/query string from window.location.search before any work was done by auth services
ProtectedpreservedlocalStorage keys that survive a logout (e.g. UI theme preference).
Override this getter in a subclass to preserve additional keys specific to your provider or application.
StaticangularFactory function to provide Angular dependencies required by Okta Stored as a static property for the factory to access without instantiation
Factory function to provide Angular dependencies required by Okta Stored as a static property for the factory to access without instantiation
Classify an error into standard error type
Converts provider-specific errors into semantic categories. Eliminates need for consumers to check error.name or error types.
ProtectedclassifyClassify Okta-specific errors into semantic types
Maps Okta error patterns to AuthErrorType enum. Updated for okta-auth-js v7.x error codes.
Error sources:
ProtectedclearClears MJ client-side caches before logout.
Removes all localStorage entries except those returned by
preservedLocalStorageKeys, and deletes the MJ_Metadata IndexedDB
database so a subsequent user session starts with a clean slate.
First, while the session is still authenticated, it sends this user's unsent realtime-call recording shards (a few seconds at most) and deletes whatever is left, so their call audio is neither left on a shared browser nor re-sent from the next user's session.
ProtectedextractExtract ID token from Okta's storage
Okta stores the JWT in IDToken.idToken This is the key abstraction - consumers never need to know about Okta's structure!
ProtectedextractExtract complete token info from Okta
Maps Okta's token structure to StandardAuthToken
ProtectedextractExtract user info from Okta claims
Maps Okta's IDToken structure to StandardUserInfo
Get ID token string (primary token method)
This is the clean abstraction - no provider-specific logic needed!
Replaces the old pattern of: claims?.__raw || claims?.idToken
Get profile picture URL from auth provider
Returns the user's profile picture URL if available from the auth provider. This abstracts away provider-specific logic:
Promise resolving to image URL or null if not available
ProtectedgetGet profile picture URL from Okta
Okta may include picture URL in user claims, similar to Auth0. If available, we can also fetch from Okta's /userinfo endpoint.
Get required configuration fields
Default implementation requires clientId. Subclasses can override to add provider-specific requirements.
Returns any constraints this provider places on the session, or null for
an unconstrained session. The host shell uses this to confine the UI (e.g.
hide app-switching and lock to a single app for magic-link sessions).
Default: unconstrained. Constrained providers override this.
Get complete token information
Returns full token details including expiration and scopes. Use this when you need more than just the token string.
Get user email as Observable stream
Get user info as Observable stream
Returns standardized user info, hiding provider-specific claim structures. No more need for consumers to merge claims or check provider-specific fields!
Handle OAuth callback
Subclasses implement provider-specific callback handling.
ProtectedhandleHandle session expiry - no-op for Okta
Okta uses refresh tokens, so it doesn't need interactive re-authentication when tokens expire. If refresh fails, the base class will throw an error and the user must log out/in manually.
Initialize the provider
Subclasses should override to set up provider-specific initialization, handle redirect callbacks, restore sessions, etc.
Check if user is authenticated (Observable stream)
Returns a reactive stream that emits authentication state changes. Consumers can subscribe to react to login/logout events.
Public login method with Observable wrapper for backward compatibility
Consumers can use either:
await this.authBase.login() (Promise)this.authBase.login().subscribe() (Observable)Optionaloptions: Record<string, unknown>ProtectedloginInternal login implementation
Subclasses implement provider-specific login flow. This is called by the public login() method.
Optionaloptions: Record<string, unknown>Logout — clears all MJ client-side caches then delegates to the provider.
Cache clearing happens universally regardless of auth provider so that a
subsequent login as a different user never sees the previous user's data.
Providers that need to clear additional caches should override
logoutInternal() and call super.logoutInternal() if applicable.
ProtectedlogoutProvider-specific logout implementation
Subclasses implement provider-specific logout flow (redirect, SDK logout, etc.).
The base class logout() calls clearClientCaches() before invoking this method,
so providers do NOT need to handle cache clearing themselves.
Refresh authentication token
Attempts to obtain a fresh authentication token using the provider's refresh mechanism. If silent refresh fails due to session expiry, the provider will handle re-authentication automatically (which may involve redirecting to the auth provider's login page).
Returns StandardAuthToken on success, or throws on complete failure.
IMPORTANT: If the provider requires interactive re-authentication (redirect or popup), this method may never return. The app will reload after authentication completes and re-initialize with a fresh token.
Promise resolving to StandardAuthToken or throws on failure
ProtectedrefreshRefresh token using Okta's token renewal
Uses renewTokens() to get new tokens silently
ProtectedupdateUpdate authentication state
Subclasses should call this when authentication state changes (after login, logout, session check, etc.)
ProtectedupdateUpdate user info
Subclasses should call this when user info is retrieved or updated. This automatically updates the email stream as well.
Validate provider configuration
Checks that all required fields are present and non-empty. Subclasses can override to add custom validation logic.
StaticAngularFactory function to provide Angular dependencies required by Okta Stored as a static property for the factory to access without instantiation
Okta authentication provider implementation - v3.0.0
Implements the abstract methods from MJAuthBase to hide Okta-specific details. The key abstraction is that Okta stores the JWT in IDToken.idToken, but consumers never need to know this detail.