When configuring a provider, auto_auth_path defines the authentication endpoint used for requests targeting that provider. Currently there is no validation that an auth method is actually mounted at that path — a misconfigured auto_auth_path silently fails at request time rather than being caught at configuration time.
This issue tracks adding a validation step that checks whether an auth method is mounted at the specified auto_auth_path when a provider is configured. If no auth method is found at that path, Warden should reject the configuration with a clear error message.
This will surface misconfiguration early, preventing silent failures during request processing.
When configuring a provider, auto_auth_path defines the authentication endpoint used for requests targeting that provider. Currently there is no validation that an auth method is actually mounted at that path — a misconfigured auto_auth_path silently fails at request time rather than being caught at configuration time.
This issue tracks adding a validation step that checks whether an auth method is mounted at the specified auto_auth_path when a provider is configured. If no auth method is found at that path, Warden should reject the configuration with a clear error message.
This will surface misconfiguration early, preventing silent failures during request processing.