Respect explicitly passed scopes on refresh

[hybrid2102]

Scope mapping was missing when preparing Request for RefreshAccessTokenAsync

[brockallen]

Can you elaborate and explain more what you felt wasn't working correctly that prompted this change?

[hybrid2102]

I apologize for not providing more details from the beginning.

In my Blazor Server application (.NET 7) I utilize this library, and I’ve observed that when the token is automatically refreshed, the scopes are not included in the request (unlike the initial token request). To address this, I attempted to pass the scopes manually using the following code snippet:

var token = await _tokenManagementService.GetAccessTokenAsync(user, new UserTokenRequestParameters { Scope = scope });

Unfortunately, it appears that the Scope parameter is not mapped in the RefreshAccessTokenAsync method.

As a result, I added the necessary mapping and submitted a Pull Request.

Is there perhaps a better way to pass the scopes in the token refresh request or instruct the library to reuse the scopes from the original request?

[josephdecock]

Looks good to me. I'm not going to add test coverage to this, because our tests are all integration tests against an identity server instance, and that doesn't use this parameter on refresh.

[josephdecock]

Thanks @hybrid2102! This will go out in our next release, and you should see a preview of that this week!