Token endpoint errors not reported correctly

[CobusKruger]

Describe the bug When the token endpoint comes back with an error, the library reports the error as ERROR OidcService code request https://sts.example.com/ with error [object Object]. Obviously, it would be much more beneficial to have the actual object content, but the entire object gets interpolated. This happens in two places:

In refreshTokensRequestTokens

const errorMessage = `OidcService code request ${this.configurationProvider.openIDConfiguration.stsServer}: ${error}`;

And in codeFlowCodeRequest

const errorMessage = `OidcService code request ${this.configurationProvider.openIDConfiguration.stsServer} with error ${error}`;

To Reproduce I'm not sure how to reliably reproduce this, but if you tamper with the code in the callback URL, that ought to do it.

Expected behavior Exactly the same error, but with the error message returned from the server intact. For example, when my token request failed, I received the following object from IdentityServer: { "error": "invalid_grant" }. Either include the JSON for the object, or report the error itself. The message should read something like this: ERROR OidcService code request https://sts.example.com/ with error { "error": "invalid_grant" }

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows
• Browser: Chrome
• Version: 83.0.4103.97

Additional context I'll be happy to make this change if you need a contributor.

[FabianGosebrink]

Hey @CobusKruger , I have seen that as well, a think to target during the next releases. If you could do a PR we would be very happy. Thanks!

[JohnGalt1717]

This is still a problem in V14.1.2.

This is what I get back: OidcService code request https://localhost:44301 Error: [object Object]

[FabianGosebrink]

I will have a look at this.

[FabianGosebrink]

Released.

[kenanaReda]

Hi! I'm using version 14.1.5 and still facing the same issue

[frk93]

@kenanaReda Did you already overcome that error? If yes, could you provide the steps you went through. I am currently experiencing the same issue on my app.

[FabianGosebrink]

Could you update to V15?

[frk93]

@FabianGosebrink I am on version 15.0.2

[kenanaReda]

@frk93 Unfortunately I couldn't fix it, and even couldn't specify the scenario to get the issue, It was showing suddenly.