Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

Invalid log message in TokenRequestValidator #774

Closed
strtdusty opened this issue Feb 3, 2017 · 7 comments
Closed

Invalid log message in TokenRequestValidator #774

strtdusty opened this issue Feb 3, 2017 · 7 comments
Labels
Milestone

Comments

@strtdusty
Copy link

  • [x ] I read and understood how to enable logging

Issue / Steps to reproduce the problem

If an authZCode.ClientID (XXXX) does not match the requested clientID (YYYY), the log message shows:
Client XXX is trying to use a code from client XXX

Current Code (line 203):
LogError("Client {clientId} is trying to use a code from client {clientId}", _validatedRequest.Client.ClientId, authZcode.ClientId);

Proposed Code:
LogError("Client {0} is trying to use a code from client {1}", _validatedRequest.Client.ClientId, authZcode.ClientId);

The log is obviously getting confused about which client ID to use.

@leastprivilege
Copy link
Member

PR?

@strtdusty
Copy link
Author

Happy to create a PR. How do I get permission to push a PR branch up? I can sign the https://cla.dotnetfoundation.org/ form but there is no IS4 project to select.

@leastprivilege
Copy link
Member

Oh - thanks for making me aware of that - the project name is wrong - you need to choose "Thinktecture.IdentityServer".

Just start with the PR - the rest will be taken care of by the "CLA Bot"

@initialspark
Copy link

This looks like it will happen on line 512 as well.

LogError("{clientId} tries to refresh token belonging to {clientId}", _validatedRequest.Client.ClientId,
refreshToken.ClientId);

So it might be worth updating your pull request with this one too.

@strtdusty
Copy link
Author

@initialspark Good catch. Updated the PR

@brockallen brockallen added bug and removed bug report labels Feb 4, 2017
@brockallen brockallen added this to the 1.2 milestone Feb 4, 2017
@brockallen
Copy link
Member

merged, thanks.

@lock
Copy link

lock bot commented Jan 15, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants