Starts in:
0 DAY
21 HRS
25 MIN
30 SEC
Starts in:
0 D
21 H
25 M
30 S
Open Closed

can not update client with secrets #3420


User avatar
0
brike.kuo@authme.com created
  • ABP Framework version: v5.3.0
  • UI type: Angular
  • DB provider: EF Core
  • Tiered (MVC) or Identity Server Separated (Angular): microservice
  • Exception message and stack trace: "The instance of entity type 'ClientSecret' cannot be tracked because another instance with the same key value for {'ClientId', 'Type', 'Value'} is already being tracked. When attaching existing entities, ensure that only one entity instance with a given key value is attached. Consider using 'DbContextOptionsBuilder.EnableSensitiveDataLogging' to see the conflicting key values."
  • Steps to reproduce the issue:
    1. add secret to client and save it
    2. edit client => update something(ex. description) except secret => save
    3. get exception

I think it's because client secrets map to "****" from 5.3.0, and UpdateClientSecrets find exist secret by value but secrets from dto will be "*****".


1 Answer(s)
  • User Avatar
    0
    maliming created
    Support Team Fullstack Developer

    hi

    It will be fixed in 5.3.3.

    see https://support.abp.io/QA/Questions/3404#answer-5bd6d8f3-7f01-53fa-6050-3a05049ffeee

Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06