How to get return value using 3rd party login?

[ghost]

I use 3rd Party Login.

The format of the access token issuance request is as follows.

https://nid.naver.com/oauth2.0/token?client_id={client_id}&client_secret={client_secret&grant_type=authorization_code&state={state}&code={code}

If the access token request succeeds, it returns a JSON-formatted value.

It has a different value from AuthConfig provided by angular-oauth2-oidc, so I putted all the required values ​​in loginUrl.

If I logged in, go to the loginurl and the resulting value appeared in browser.

What I want is to get a return value.

What should I do in this case?

[jeroenheijmans]

You question is a wee bit hard to follow (and a block of formatted code (text) would be nicer than a screenshot), but from what I see I think you might have things backwards a bit.

Two things I notice from your URIs is:

1. You pass all parameters already in the URI, but the library should be setting them instead (grant type, secrets, etc). If your server supports it, check out the /.well-known/openid-configuration endpoint, and you'll see it lists a token and/or authorize endpoint without any parameters yet. For comparison, check this example, or this one.
2. You seem to want to use the Authorization Code flow, but see Announcement: Version 8 is coming #549 (and Support for Authorization code with PKCE #470, support Authorization Code Grant #507): this flow is not yet supported as of versions < 8.

So with current versions, you'd have to rewrite your app to rely on Implicit or Password (legacy) flows.

[ghost]

@jeroenheijmans
Thanks in advance for the answers.
I'll give you one more basic question.
What is the function to request a token?
initImplicitFlow() works just like window.open().

[jeroenheijmans]

That's not really easy to answer, I recommend first reading up about the implicit flow and possibly the password flow, before continuing implementation of oauth2/oidc in your app.

[jeroenheijmans]

Hoping the questions got sufficiently answered (for as far as we reasonably can on the issues list of this specific library).

Let us know if you have any specific open issues left with this library, either here so we could reopen, or in a fresh issue.