I’m using okta login with Express. When I run it on a server, it does call the loginCallback function that I specify on new ExpressOIDC config. But when I use the same okta app on another server, it’s not being called, instead after login it shows a 404 saying that loginCallback path does not exist. I create a loginCallback to handle the redirect, but then I have no access to req.userContext.
const oidc = new ExpressOIDC({
issuer: "{issuer}",
client_id: "{client_id}",
client_secret: "{client_secret}",
appBaseUrl: "http://localhost:3000",
redirect_uri: "http://localhost:3000/loginCallback",
scope: "openid email profile",
routes: {
loginCallback: {
path: "/loginCallback",
handler: (req, res, next) => {
console.log("req", req.userContext.tokens);
res.redirect("/");
},
}
}
});
Above code is not running in a server but it’s on the other.
server.get('/loginCallback', async (req, res, next) => {
console.log("here!", req)
});
this does get called but can’t access the userContext obj.