Hello! I'm implementing an openid connect authentication with Gluu and I have a custom application which handles the login. I am implementing the Authorization code flow with two phase authentication. What is the correct way to implement a cancel functionality in the login flow with Gluu? The login application has a "cancel" button, if the user decides to not authenticate. The desired behavior would be to redirect the user back to the relying party with an error payload saying something like: "User did not authenticate" This is similar to the Authorization code flow, where the user authenticates successfully and then gets redirected back to the relying party with an authentication code. With the cancel button I would like to do a similar redirect, but with an error payload. I have read about the LogoutAction, but my understanding is that it should be used for performing a logout for a user that has already authenticated. Is this correct or am I miss understanding something? It would be possible to do a javascript redirect directly from the login application, but this approach has a drawback in the two phase authentication. If the user decides to cancel the authentication in the second phase, the session and other intermediate state should be cleaned up, but this will not happen if I implement a javascript redirect from the UI directly. Or is there a method in the Gluu that will do this cleanup/logout if I call it from a custom script? I'm already using a custom python script to integrate gluu with the login application. What is the correct way to implement this? br, Jarkko