Is there any way to set an authorizationEndpoint on a call to login()?

[danjenkins]

I need to have different authorizationEndpoint settings for different providers, from what I can see in the code, authorizationEndpoint is always retrieved from the config that was set on the Provider.

Needing to change the config on the provider depending on which button ic clicked/pressed seems counter intuitive... Looks like you can pass in additionalParams on calling login() but the authorizationEndpoint is always retrieved from config.

Am I right in what I'm reading in the code?

[soofstad]

Hi @danjenkins
That's right. You can only set "authEndpoint" in the config object.
If you provide a scenario where this feature would be needed, we can discuss supporting it 🙂

[danjenkins]

After making the discussion topic I thought how I could do this without needing to change the authorizationEndpoint locally... if I point the authorizationEndpoint at a url I control and have that endpoint redirect to the correct endpoint...

I'm using workos and their authkit product... you end up with different authorization urls depending on providers you're using etc...

[sebastianvitterso]

Would it not be possible for you to modify your configuration object values depending on user actions? Using a useState to contain the authEndpoint, and then modifying this depending on user input would work with regards to the library, so maybe it's something you could implement in the application logic?

[danjenkins]

Yeah, that just felt unnecessary to me, I'd be changing state layers up from the sign in button just to change where the authorizationEndpoint was... ultimately you could end up with a timing issue too. It seems to me like authorizationEndpoint can be different per provider, so if you're enabling auth with multiple providers, its something that would need changed per login function depending on who you're logging in with.

I think I can get around it by calling an endpoint I'm in control of and let redirect to the right place which maybe is a nicer solution all round?

[sebastianvitterso]

At this point you're starting to do some of the work done by the library.
I think the easiest solution is to use the useState-solution to switch between configs.

I would also assume that your configs would differ depending on which auth-provider you're using, meaning you might want to have diffent configs set when the user returns from the redirect? I would use some sort of useLocalStorage-hook to ensure this is stable before and after the redirect.

If you decide to go forward with the controlled redirect, and it works with the rest of the config being the same, I don't see an issue, but again you're starting to do the library's work.