Hello. My understanding of the OIDC RP initiated logout flow for hydra is: • Call end_session_endpoint with post_logout_redirect_uri and id_token_hint • Hydra redirects to urls.logout with logout_challenge • Custom UI responsible for: calling hydra accept logout endpoint with logout_challenge and then redirecting user agent to post_logout_redirect_uri (from hydra accept logout response body) My understanding is that if the hydra+kratos integration is enabled on the hydra side (e.g. set urls.identity_provider.url to the kratos admin endpoint), then the kratos session should be disabled as part of this flow. Is this the case? I want to ensure I understand which conditions the kratos session is disabled (or not). Some specific questions: 1. Does frontchannel/backchannel logout need to be called (even an empty url) for the kratos session to be invalidated, or can those urls be empty and the session still invalidated? 2. Does anything more than the hydra Get/AcceptLogout request need to be called to make the kratos session invalidation work? 3. Are there cases where calling the hydra end_session_endpoint might return immediately to the post_logout_redirect_uri? Maybe if the id_token_hint is null or the hydra/kratos session cookies are not sent?