r-same-local-auth-v1-azure-ad-deferred
R-Same v1 uses local authentication (argon2id + mandatory TOTP + JWT in HttpOnly cookies) because Runwal’s Azure AD infrastructure is not yet complete. Azure AD SSO is deferred to v1.5 with stub interfaces only in v1. Migration path on Azure AD completion: dual-mode → per-user email-match → deprecate local. Do not enable direct Azure AD flows until the Runwal AD work is confirmed done.
Related
- r-dash-azure-ad-deferred-local-auth-v1-stack
- r-dash-auth-amendment-local-auth-v1-azure-ad-sso-deferred
- r-same-azure-ad-sso-deferred-local-auth-v1
- runwal
- claude-desktop-custom-connector-requires-oauth-not-bearer
- azure-ad-sso-deferred-local-auth-migration-path
- azure-ad-sso-deferred-local-auth-v1-stub-interfaces
- r-same-local-auth-v1-azure-ad-sso-deferred
- r-same-azure-ad-sso-deferred-v1-local-auth-only
- azure-ad-sso-deferred-v1-uses-local-auth
- pwa-push-notifications-require-vapid-push-handler
- azure-ad-sso-deferred-local-auth-v1-because-runwal-ad-incomp
- azure-ad-sso-deferred-local-auth-is-v1
- r-same-azure-ad-deferred-local-auth-v1