Since we moved to grant one of three things can happen:
If a provider is disabled and you visit /signin/provider/$disabledprovider hasura-auth will go to the redirect url with the query arg ?error=disabled-endpoint&errorDescription=This+endpoint+is+disabled.
If a provider is enabled and configured, everything follows the expected workflow
If a provider is enabled but misconfigured in some way, a 404 is returned when visitin /signin/provider/$disabledprovider.
Ideally we would:
On startup log which providers are being enabled
If there is an issue with a provider, be clear about it on the logs
When visiting /signin/provider/$misconfigured-provider log there is an issue on the logs and go to the redirect url with something like ?error=misconfigured-provider&errorDescription=This+provider+is+misconfigured
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Since we moved to grant one of three things can happen:
/signin/provider/$disabledprovider
hasura-auth will go to the redirect url with the query arg?error=disabled-endpoint&errorDescription=This+endpoint+is+disabled
./signin/provider/$disabledprovider
.Ideally we would:
/signin/provider/$misconfigured-provider
log there is an issue on the logs and go to the redirect url with something like?error=misconfigured-provider&errorDescription=This+provider+is+misconfigured