Angular-oauth2-oidc: JWKs fields are null at validation

[dustingallegos]

_Full disclosure_
_This might not be an issue and/or just me not knowing how to use the library correctly :)
So thank you for your help ahead of time!_

So after logging in, I get the token back from the parameters by invoking the TryLogin method but it fails at validation time with an error: Parameter jwks expected! (see image below)

When I inspect the params object, I can effectively see that the jwks field is empty

However, I do see in the token header the fields corresponding to the jwks from where the public key can be composed. Maybe I'm wrong?

Additionally, I understand that by convention, the jwks fields can also be obtained from the
http://localhost:5000/.well-known/openid-configuration end point which it does give me the jwks when hitting it:

Am I missing an important step? Any help would be appreciated :)

[manfredsteyer]

Thx for this info.
Which Identity-Solution do you use?
Can you send me your discovery document and the document with the keys (jwks)?

[dustingallegos]

No problem.
Identity Server 4, which has an standard Oauth 2.0 generated discovery document. More information here -> http://docs.identityserver.io/en/release/topics/discovery.html?highlight=discovery%20document
Besides that, I'm not sure what I can send you.. perhaps the text itself shown in the page?
Let me know - Thanks a lot!

[manfredsteyer]

Oh, when its IdSvr4 then the discovery document should be fine.

Do you call tryLogin after loadDiscoveryDocument, e. g. within the then-block?

    this.oauthService.loadDiscoveryDocument().then((doc) => {
      this.oauthService.tryLogin();
    });

I'm aksing b/c otherwise tryLogin could be called before the config data arrived.

Are there warning or error messages on the javascript console?

When happens, when you add the following code, when setting up the lib?

this.oauthService.events.subscribe(e => {
    console.debug('oauth/oidc event', e);
})

When does this write to the console?

[dustingallegos]

using the tryLogin() inside the loadDiscoveryDocument() did the trick!
Thanks a lot for responding quickly! :)

[felipecaparelli]

I am getting the same error... but in my case, I'm using the okta server as suggested by the example. I've just changed the clientId and the root URL (https://dev-{MY_ID_HERE}.oktapreview.com)... Did I forget anything?