StartIdentityProviderIntent gRPC Issue
The gRPC
2. REST API with service account auth ā Works!
Is the gRPC endpoint intended only for user-session context, while backend services should use the REST API? The docs don't clarify this distinction.
This works perfectly and returns the expected
---
Environment: Zitadel v4.2.0 protobuf definitions, self-hosted Docker, SAML 2.0 IdP
Slightly concern about using a REST API workaround given the deprecation notice?
StartIdentityProviderIntentStartIdentityProviderIntent endpoint returns an empty response (only detailsdetails field) when using service account JWT authentication, but the REST API equivalent (POST /v2/idp_intentsPOST /v2/idp_intents) works perfectly with the same auth.What We Tried
1. gRPC with service account auth ā Empty response2. REST API with service account auth ā Works!
Server Logs
Is the gRPC endpoint intended only for user-session context, while backend services should use the REST API? The docs don't clarify this distinction.
Workaround
We're using the REST API instead:This works perfectly and returns the expected
formDataformData for SAML POST binding.---
Environment: Zitadel v4.2.0 protobuf definitions, self-hosted Docker, SAML 2.0 IdP
Slightly concern about using a REST API workaround given the deprecation notice?
