You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using for an example Azure connection, one will always be logged back in. Federated logout would fix this.
Describe the ideal solution
Could maybe create a new config, logoutParams, which will accept a federated key with a boolean value. It might even accept postLogoutRedirect, but that would require a major bump (unless you accept both locations, but just deprecate the current one).
Alternatives and current work-arounds
I've made a workaround by creating the URL myself and append &federated. Also disable the logout route by setting routes: { logout: false } in the config.
constlogout=async(req: Request,res: Response)=>{// Logs the user out locallyreq[authConfig.session.name]=undefined;constreturnTo=authConfig.baseURL;constlogoutURL=newurl.URL(`${authConfig.issuerBaseURL}v2/logout`);logoutURL.search=querystring.stringify({client_id: authConfig.clientID,
returnTo,})+'&federated';res.redirect(logoutURL.toString());};
The text was updated successfully, but these errors were encountered:
Describe the problem you'd like to have solved
When using for an example Azure connection, one will always be logged back in. Federated logout would fix this.
Describe the ideal solution
Could maybe create a new config,
logoutParams
, which will accept afederated
key with a boolean value. It might even acceptpostLogoutRedirect
, but that would require a major bump (unless you accept both locations, but just deprecate the current one).Alternatives and current work-arounds
I've made a workaround by creating the URL myself and append
&federated
. Also disable the logout route by settingroutes: { logout: false }
in the config.The text was updated successfully, but these errors were encountered: