Hello,

I'm currently trying to implement linkings between Identity Providers and FusionAuth accounts.
This works pretty good and the whole connect/authorization workflow runs flawlesly. Though, when using the Pending Link strategy, the user does not get linked at the end (although he is logged in, etc.). However, if I use the Link-on-email strategy for example, the user gets linked without a problem.

I got no logs and no errors, apart from this message from the Debug Event Log of the Identity Provider (Discord): 3/1/2022 04:11:04 PM GMT The link must now be completed using the Link API.
Furthermore, the workflow redirects to the same page where it started, but it has additional parameter: ?code=XXX&locale=en&state=XXX&userState=Authenticated.

Apart from that, I really have no clues about this problem. I know my information is rather meagre, so if you have any additional questions, just ask.

Best regards

@joshua

So, you say, the only thing I can do at the moment is to request a new feature and to be patient?

Or can I use this request, which then links to discord via the redirect_uri?

GET /oauth2/authorize?client_id={client_id}&redirect_uri={redirect_uri}&response_type=code&tenantId={tenantId}

But, thanks so far for you help,
Chriss

@joshua

Yeah, I already thought so, that this way of using is not directly intended.

I have a dashboard for linking user accounts with our own accounts. We want to use FusionAuth for that, so we try to send the user from the button of our own website directly to the link provided by Discord.

Does FusionAuth provide some kind of that link?

Thanks too for helping,
Chriss

@joshua

No, absolutely not. I could easily follow the whole documentation.
If you want so, everything works fine. If I activate the "Login via Discord" button in FusionAuth, I can login with Discord. But, if I don't want to use the button, but instead the provided link by Discord, it doesn't work.

I think, FusionAuth creates some kind of "session" when using 3rd-party OAuth, which does not work, when you get sent back to FusionAuth directly by Discord and not FusionAuth itself. (I hope it was clear enough)

Thanks for you reply,
Chriss

Description

After successfully creating an OpenID Identity Provider, you can activate the registration for a FusionAuth app, so you can register with a UI button via the specific provider.
Though, if you try to use the direct link by your 3rd party service application, you get the following error:

{
  "error" : "invalid_request",
  "error_description" : "The request is missing a required parameter: redirect_uri",
  "error_reason" : "missing_redirect_uri"
}

To be a little more specific, I created my Discord Identity Provider, which I wanted to use via the link I get from the Discord Application:

This link however does not work as I get the error above. On the other hand, the button to register, which FusionAuth provides, does work.
Though, I need for my service the direct link (because I'm having my own buttons, etc.), which does not work.

Am I making something absolutely wrong or does FusionAuth simply not provide the needed functions?

My Configuration

The link I get from the Discord Application (which includes a redirect_uri) :

https://discord.com/api/oauth2/authorize?client_id=XXX&redirect_uri=https%3A%2F%2FXXX%2Foauth2%2Fcallback&response_type=code&scope=identify email

My FusionAuth Identity Provider configuration:

PS: No debug or other logs appear.