You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ServiceClient handles S2S Token Caching and supports 2 forms of token caching for User PW flows... either in Memory or File. If you want to use other token caching processes, currently, you need to use external auth and implement the caching mechanic of your choice.
Regarding Managed Identity and automatic certificate rollover flows (SubjectName Auth), we do want to add support for those in the future but have yet to work though the issue related to them. As both of those flows have a strong Azure dependency, and have behavorial differences between various Azure hosts, we would like to deal with them as AddOn packages for the ServiceClient vs built in feature.
Activity
MattB-msft commentedon Jan 28, 2022
The ServiceClient handles S2S Token Caching and supports 2 forms of token caching for User PW flows... either in Memory or File. If you want to use other token caching processes, currently, you need to use external auth and implement the caching mechanic of your choice.
Regarding Managed Identity and automatic certificate rollover flows (SubjectName Auth), we do want to add support for those in the future but have yet to work though the issue related to them. As both of those flows have a strong Azure dependency, and have behavorial differences between various Azure hosts, we would like to deal with them as AddOn packages for the ServiceClient vs built in feature.
fowl2 commentedon Jan 29, 2022
Absolutely and with the library story is still being in so much flux at the moment it's totally understandable.
Just thought I'd register the interest in our bold secretless future and help any others that want to give it a go today :)