Open Vaccano opened 1 year ago
Hey @Vaccano. Graph Explorer does not support application permissions because of the security vulnerability caused by exposing your client secret and clientID to the web. The authentication provider that we use also does not support this by default because of the same reasons.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
@Onokaev - That makes sense. However, getting an Access Token for a client credentials login is not too hard, and they expire fairly quickly. Maybe consider allowing the input of a Client Credentials access token and using it in the Graph Explorer?
Sure thing @Vaccano. Let me log this as a feature request
I would like to test operations using client credentials logins. (Client ID and Client Secret.) My scenario is that I have an application that has created other applications. (So it the child applications has the owner set to the parent application). I would like to use Graph Explorer to test out what operations are allowed in that scenario.
Describe the solution you'd like I would like a way for the access token used by Graph Explorer to be generated from a Client ID and Client Secret.
Describe alternatives you've considered I did think about getting an access token from powershell and then swapping out the access token used by Graph Explorer (on the Access Token tab). But that tab is read only.