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
At the moment, if you don't specify successUri and failureUri settings for a provider, you just end up with an exception. THe plugin should really use a sensible default if those settings haven't been provided.
I originally thought successUri should be '/' by default, but then that leaves a big question mark over the default for the failure URI. Perhaps the defaults should be /oauth/success and /oauth/failure? Then the controller could provide default action implementations.
The text was updated successfully, but these errors were encountered:
I reckon this is not a bad idea. At least then you'd have a differentiator. Not sure what format the default action should take though - perhaps a simple page like the Grails error page?
I think a basic view that uses either the default application layout or 'main' would work. I think using 'main' layout is the best approach as not every project has a default application layout.
At the moment, if you don't specify
successUri
andfailureUri
settings for a provider, you just end up with an exception. THe plugin should really use a sensible default if those settings haven't been provided.I originally thought
successUri
should be '/' by default, but then that leaves a big question mark over the default for the failure URI. Perhaps the defaults should be/oauth/success
and/oauth/failure
? Then the controller could provide default action implementations.The text was updated successfully, but these errors were encountered: