Hey there. We have this OAUTH_CALLBACK_URL env which is used to redirect back to vVuch after auth in OAuth system. But i believe we don't have any analog for logout? As far as i understand, VOUCH_POST_LOGOUT_REDIRECT_URIS param works only for vouch /logout endpoint. If it does redirect to some OAUTH_END_SESSION_ENDPOINT - it won't pass the redirect link into it (e.g. Okta's post_logout_redirect_uri). This makes OAUTH_END_SESSION_ENDPOINT effectively unusable since you actually want to add OAuth logout with redirect into VOUCH_POST_LOGOUT_REDIRECT_URIS with all required parameters (there is an example for this in docs). For Okta it is impossible to use as well since it required id_token_hint which you can't include into redirect uris (also makes mentioned doc incorrect since it shows Okta url without id_token_hint).
So basically my point is that you can't make Vouch construct the OAuth link like this:
https://okta.com/oauth2/v1/logout?id_token_hint=123&post_logout_redirect_uri=https://myproject.com
Is it possible to implement something like this?
Hey there. We have this
OAUTH_CALLBACK_URLenv which is used to redirect back to vVuch after auth in OAuth system. But i believe we don't have any analog for logout? As far as i understand,VOUCH_POST_LOGOUT_REDIRECT_URISparam works only for vouch /logout endpoint. If it does redirect to someOAUTH_END_SESSION_ENDPOINT- it won't pass the redirect link into it (e.g. Okta's post_logout_redirect_uri). This makesOAUTH_END_SESSION_ENDPOINTeffectively unusable since you actually want to add OAuth logout with redirect intoVOUCH_POST_LOGOUT_REDIRECT_URISwith all required parameters (there is an example for this in docs). For Okta it is impossible to use as well since it requiredid_token_hintwhich you can't include into redirect uris (also makes mentioned doc incorrect since it shows Okta url withoutid_token_hint).So basically my point is that you can't make Vouch construct the OAuth link like this:
Is it possible to implement something like this?