microsoft/Atlas

Isolate token caches by input parameters

lodejard opened this issue · 0 comments

Token cache files should be isolated (different file names on disk) by various auth parameters.

  • Different tenant (or authority) values should mean there is no overlap between credentials used.

  • A different client app id should also mean the tokens have no overlap.

  • The resource (or scope) values probably shouldn't have isolated token stores...