B2C Support for client credential flow.
To enable APIs to use authentication from another application with separate security credentials (clientId+secret). Needed for APIs to make graph calls.
(This is not the same as on-behalf-of flow, which represents the ability to exchange an access token intended for one audience for an access token intended for a different audience)
This is not planned for the next 6 months, but is on the roadmap.
Hi, when will there be an update?
Hrvoje Kusulja commented
I am also interested in this very much....
Dekel Asaf commented
Any update on that?
Pahne, Andy (external) commented
Any news on that? Seems like an improtant feature.
This seems like such an essential feature...
Is this the same issue as this other one (with more votes)?
Koushik Mondal commented
Any updates for the production release of client credential flow
Simon Steele commented
Specifically interested to be able to make Graph calls for Microsoft users, to get access to their email/calendars etc...
I believe the workaround at this stage is to authenticate with Azure AD directly, rather than going via Azure AD B2C.
dotan raz commented
Would appreciate a server side deamons support for adb2c for exposing strict policy for 3rd party partner applications
Lots of copies of web apis, each configured with different clientids as far as I can tell.. or everything in your entire site using one clientid (applicationId)
Ha Duong commented
While waiting for the Azure B2C team to review this Anyone know what is the work around I can look into at the moment please?