OAuth Token Management Issue

[B-HOLLEY]

I believe I've found an issue in Oauth2TokenManager.cs.

https://github.com/OneSpan/oss.sdk.net/blob/dev/src/SDK/Oauth/Oauth2TokenManager.cs#L33

Notice the SDK thinks the oauth token expires in 2080. The issue seems to be with the following:
long unixEpochTime = (long)payloadJson["exp"]; DateTime tokenExpiresAt = DateTime.UtcNow.AddSeconds(unixEpochTime); DateTimeOffset now = DateTimeOffset.Now;

unixEpochTime is a timestamp (number of seconds from 1\1\1970). You're taking the number of seconds since 1970, and adding it to the current current UTC time, which setting the expiration way into the future. Since the token actually expires in 5 minutes, we cant wait until 2080 for the SDK to think the token is expired :)

[dlcannons]

@B-HOLLEY Have you gotten any updates to this issue or your linked PR? Or perhaps a work around with the current SDK?

This bug completely breaks us using oAuth2.0, as the integration breaks after 5 minutes.

[B-HOLLEY]

@B-HOLLEY Have you gotten any updates to this issue or your linked PR? Or perhaps a work around with the current SDK?

This bug completely breaks us using oAuth2.0, as the integration breaks after 5 minutes.

No feedback or workarounds...pretty frustrating. I've been using a local build based on my PR for a while now and havent gotten any complaints. If you want to go the same route I went (e.g. DIY fix), the only change you really need is on src/SDK/Oauth/Oauth2TokenManager.cs from my PR.

[houjianyu]

Hi @B-HOLLEY and @dlcannons, the issue you've found will be taken into consideration in our next release. We have created an internal ticket PB-119997 for it. Thanks for your patience.

[houjianyu]

Hello @B-HOLLEY I made the change according to your suggestions at #138, but since your pull request has some other minor changes so I won't take your pull request. Thanks!