Login V1 + Actions V2: alternatives to "(Actions V1) External Authentication / Post Authentication"?
š¬Self-hostedāQuestionāUnsolvedšŖ²Bugs
Is there any alternative to '(Actions V1) External Authentication / Post Authentication' on Actions V2 when using Login V1?
I see on the documentation (Migrate from Actions v1 to v2) suggestions to use the response of
I'm running Zitadel self-hosted, mostly on Zitadel v3.4.2, but also tried with Zitadel v4.6.2 and confirmed that
Is this expected or a bug? I don't see it mentioned anywhere in the documentation that those should only work with Actions V2.
Is there any alternative to those if I want to execute an action following to external authentications (using Actions V2)?
I see on the documentation (Migrate from Actions v1 to v2) suggestions to use the response of
/zitadel.user.v2.UserService/RetrieveIdentityProviderIntent/zitadel.user.v2.UserService/RetrieveIdentityProviderIntent, however from my own testing I see that action executions on that response are not triggered when using Login V1, only when using Login V2. I've tried with a few other similar responses, and none of them were triggered when using login V1 after a successful external authentication either:I'm running Zitadel self-hosted, mostly on Zitadel v3.4.2, but also tried with Zitadel v4.6.2 and confirmed that
/zitadel.user.v2.UserService/RetrieveIdentityProviderIntent/zitadel.user.v2.UserService/RetrieveIdentityProviderIntent is not triggered when using Login V1 on that version either...Is this expected or a bug? I don't see it mentioned anywhere in the documentation that those should only work with Actions V2.
Is there any alternative to those if I want to execute an action following to external authentications (using Actions V2)?
