Wolfspyre
Chevereto Member
Describe your feature request
The process of setting up login providers isn't egregiously complicated,
however I think that it might make things a little easier for the average user if the expected callback URL was amalgamated
Alternatively, providing a simple
at the top of the
would likely be pretty simple to do, and I'd imagine it would be a nice quality-of-life improvement; but ¯\(ツ)/¯
Where did you see this?
Many tools I've used provide a bit more guidance on how the specific app expects to interact with an external entity... this isn't much different, really.
Community interest
IDK how good an idea this is 😉 but ¯\(ツ)/¯
The process of setting up login providers isn't egregiously complicated,
however I think that it might make things a little easier for the average user if the expected callback URL was amalgamated
(proto)+(site)+/connect/(provider)/ and provided for the user...Alternatively, providing a simple
"The callback URL is the amalgam of (rendered-site-uri)/connect/(auth-provider-keyname)/"
at the top of the
/dashboard/settings/login-providers route pagewould likely be pretty simple to do, and I'd imagine it would be a nice quality-of-life improvement; but ¯\(ツ)/¯
Where did you see this?
Many tools I've used provide a bit more guidance on how the specific app expects to interact with an external entity... this isn't much different, really.
Community interest
IDK how good an idea this is 😉 but ¯\(ツ)/¯