Hello,
I'm trying to setup Microsoft for headless authentication but the only option seems to be provider_redirect. Is my configuration incorrect or this is a known limitation?
Hello,
I'm trying to setup Microsoft for headless authentication but the only option seems to be provider_redirect. Is my configuration incorrect or this is a known limitation?
I am also curious about this, doesn't seem like it should be the case but I might be wrong. trying to look at customizing things but was hoping there was a way around that
I have this exact same issue. Would love some guidance.
I am not sure I understand the issue. It talks about client=app, and then mentions
but the only option seems to be
provider_redirect
... but with client=app provider_redirect is not an option at all. That is intentional as provider_redirect initiates and completes the whole OAuth handshake in a browser, and there is no way to transfer the authenticated state at the end of the handshake from the browser to the app.
As for using provider_token, the microsoft provider does not implement a verify_token() method and hence doe snot support token authentication yet. The OpenID Connect provider does -- so perhaps you can hookup the provider as a regular OIDC provider and use provider_token ?
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?