The current implementation uses the OAuth implicit grant which indeed relies on a user to log-in. Implementing application level login needs a server-side proxy which should authenticate against Azure. While technically possible it would need additional configuration such as specifying which Graph API’s to proxy.
Do you mean Radzen’s implementation? If yes - no, the Azure AD login sequence is implemented at the client-side via Angular service that Radzen generates.
While technically possible it would need additional configuration such as specifying which Graph API’s to proxy
Not sure if that’s so. I think you just need to get the id_token using server-side to avoid CORS. But with the token, the graph calls should be all the same from the client, no?
Oh I see what you mean - you want to access the Graph API under the same account always.
Sort of. I don’t want to authorize with delegated user permissions, rather I want to access under the app permissions specified in app registration using the ‘client consent’ flow.
I would think you could simply add a checkbox for Client Consent grant type and then options to specify tenant and client secret. Then POST to the \token endpoint to get the id_token. Like so:
POST /{tenant}/oauth2/v2.0/token HTTP/1.1
Host: login.microsoftonline.com
Content-Type: application/x-www-form-urlencoded