Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Ensure updates to state are done atomically in ConfigurationManager #3142

Open
1 of 14 tasks
keegan-caruso opened this issue Feb 21, 2025 · 0 comments
Open
1 of 14 tasks
Labels
Bug Product is not functioning as expected Internal Indicates issue was opened by the IdentityModel team

Comments

@keegan-caruso
Copy link
Contributor

Which version of Microsoft.IdentityModel are you using?
Note that to get help, you need to run the latest version.
Microsoft.IdentityModel 8.5.0

Where is the issue?

  • M.IM.JsonWebTokens
  • M.IM.KeyVaultExtensions
  • M.IM.Logging
  • M.IM.ManagedKeyVaultSecurityKey
  • M.IM.Protocols
  • M.IM.Protocols.OpenIdConnect
  • M.IM.Protocols.SignedHttpRequest
  • M.IM.Protocols.WsFederation
  • M.IM.TestExtensions
  • M.IM.Tokens
  • M.IM.Tokens.Saml
  • M.IM.Validators
  • M.IM.Xml
  • S.IM.Tokens.Jwt
  • Other (please describe)

Expected behavior

Ensure updates to state are done atomically in ConfigurationManager.

See #3090, these changes showed a viable way to handle this. It would need small changes to work with 8.5.0

Actual behavior

_syncAfter and _lastRequestRefresh do not have guaranteed atomic updates.

@keegan-caruso keegan-caruso added needs attention untriaged Bug Product is not functioning as expected Internal Indicates issue was opened by the IdentityModel team and removed needs attention untriaged labels Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Product is not functioning as expected Internal Indicates issue was opened by the IdentityModel team
Projects
None yet
Development

No branches or pull requests

1 participant