You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.
As of v0.6.0 the setUpSuccessRedirect and setUpSuccessRedirect parameters have been removed in favor of checking if the routes are equal to the defaults. So now I can't use /auth/success or /auth/failure with my own routes and are forced to have it send the public/auth-success.html and public/auth-fail.html files. There should be an option of using those defaults without being forced to have those specific html files.
The text was updated successfully, but these errors were encountered:
As of v0.6.0 the
setUpSuccessRedirect
andsetUpSuccessRedirect
parameters have been removed in favor of checking if the routes are equal to the defaults. So now I can't use/auth/success
or/auth/failure
with my own routes and are forced to have it send thepublic/auth-success.html
andpublic/auth-fail.html
files. There should be an option of using those defaults without being forced to have those specific html files.The text was updated successfully, but these errors were encountered: