Charles Lowell

Great, I'm glad azd is unblocked. The v1.0.0 API including `cache.ExportReplace` is stable, please feel free to contribute doc updates.

Reopening because #456 didn't merge and it's still impossible to unmarshal a partitioned cache

This issue is still relevant but note that this is all internal code so, the confusion isn't customer-facing. Concretely, the weirdness is - Leg 1: `public.Client` requests an auth code...

Blocked on https://github.com/AzureAD/microsoft-authentication-library-for-go/issues/239

🤔 on second thought I believe the only change we need from MSAL is to expose any `refresh_in` value provided by the STS. Everything else should be feasible in azidentity/azcore....

On third thought, this is blocked because MSAL's token cache has a [hardcoded expiration time](https://github.com/AzureAD/microsoft-authentication-library-for-go/blob/ae2db6b72c7010958355f448e99209bd28e76e67/apps/internal/base/internal/storage/items.go#L128-L130) preventing us from acquiring a new token when a cached one has at least 5...

Can you please explain how the lack of this feature makes track 2 unusable? What breaks when your application gets a token valid for 24 hours? And how does track...

I think I'm getting the gist of this: - `azidentity` uses a 5-minute refresh window for tokens i.e., it refreshes cached tokens when their expiration is less than 5 minutes...

Thanks for opening this issue! You're quite right that `cache.New` does nothing to prevent conflict between multiple processes, and it should. I think we don't want to synchronize processes with...

Well, yes and no. Yes, because the storage implementation itself isn't concurrency-safe. No, because `cache.New()` wraps that storage implementation in a caching layer that is concurrency-safe. As used by azidentity...