@azure/identity-cache-persistence overwrites Microsoft.Developer.IdentityService entry in the keychain across different applications.

[altinokdarici]

• Package Name: @azure/identity-cache-persistence
• Package Version: 1.1.0
• Operating system: Mac OS
• [x] nodejs
  • version: 18.19.1
• [ ] browser
  • name/version:
• [x] typescript
  • version:
• Is the bug related to documentation in
  • [ ] README.md
  • [ ] source code documentation
  • [ ] SDK API docs on https://docs.microsoft.com

Describe the bug @azure/identity-cache-persistence overwrites Microsoft.Developer.IdentityService entry in the keychain across applications.

To Reproduce Scenario: There are two different applications using @azure/identity-cache-persistence. Application A has the following configuration;

export const tokenCachePersistenceOptions: TokenCachePersistenceOptions = { enabled: true, name: 'appA', };

Application B has the following config:

export const tokenCachePersistenceOptions: TokenCachePersistenceOptions = { enabled: true, name: 'appB', };

User runs the app A, authentication happens and the token gets stored in the KeyChain with the entry name: Microsoft.Developer.IdentityService

User runs the app B, @azure/identity-cache-persistence reads the KeyChain with the entry name: Microsoft.Developer.IdentityService and authentication fail (or interactive auth happens again) because this entry stored by app A.

Expected behavior Each application should have its own entry in the KeyChain regarding the configuration. ie: Microsoft.Developer.IdentityService-appA and Microsoft.Developer.IdentityService-appB

[github-actions[bot]]

@KarishmaGhiya @maorleger

[github-actions[bot]]

Thank you for your feedback. Tagging and routing to the team member best able to assist.