-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for SPA based application clients using PKCE flow #286
Comments
Hi @autom8ter, thanks for requesting this! It doesn't look like we're able to support SPA reply/redirect URLs at present but we'll revisit this as soon as we are able. Long explanation: I originally thought this might be an easy implementation with MS Graph, but it looks like support hasn't been added there yet. Tracing the portal, this makes use of AAD Graph to patch the application with the |
@manicminer I think it should be possible to implement it. when i send the following patch request it works https://graph.microsoft.com/v1.0/applications/(appObjId) { |
@SvenHamers That's great, thanks for reporting a working request with MS Graph 👍 |
highly interested in this as well. As workaround we added this in an
|
Hi, |
This comment has been minimized.
This comment has been minimized.
It looks like this will be supported in #474 so I'm looking forward to a new version. Currently have to change this manually in Azure Portal otherwise the app I deploy doesn't work. Kind of surprised that "web" exists but "spa" did not. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
Add support for SPA based clients using PKCE flow. PKCE flow is available if "Single-page Application" is selected on the "Authentication" tab of an App Registration in the Azure portal. Here is a screen shot showing a PKCE configuration:
The terraform provider is not useable for SPA based clients in its current form.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: