Use-case: Authenticating students in a future educational web application by IdP brokering Environment: self-hosted Version: 4.13 Stack: Webapp does not yet exist, experimenting with the Flask example (https://zitadel.com/docs/sdk-examples/flask), except using SAML instead of OIDC
What you expected to happen: I authenticate against the IdP with SAML PKCE (works all fine), then give my consent to attribute release inside IdP (works all fine), then the Zitadel account creation dialogue opens. I configured an action that says api.setEmail("example@gmail.com"). I expected this to show up in the dialogue.
What went wrong: The dialogue is all empty. It is not clear if my action even runs. As I hardcode the e-mail, this is (hopefully) not directly related to the SAML attributes, which I plan on mapping later. For now I am just trying to get something pre-set to show up in the Zitadel dialogue.