Greetings,
After several years of running Open OnDemand, a customer has finally tried to log out, which exposed a gap in my configs.
The server name is bananas(.)tree(.)company(.)net , but clients use ondemand(.)tree(.)company(.)net to make it more transparent to clients when the back-end server gets an update.
While in beta, I only used the bananas hostname, until it was promoted to production (behind the ondemand CNAME). Logging out works aok in the bananas hostname, but when clients try to log out via the ondemand URL (https(:)//ondemand(.)tree(.)company(.)net/oidc?logout=https%3A%2F%2Fbananas(.)tree(.)company(.)net), I get the error:
URL value “https(:)//bananas(.)tree(.)company(.)net” does not match the hostname of the current request “ondemand(.)tree(.)company(.)net”
In looking through configs, I have been unable to convince myself that I have found a way to properly configure the logout action to allow for bananas, as well as ondemand logout links
I am using dex for auth, and I am eyeing the dex config set for id:https(:)//bananas(.)tree(.)company(.)net which seems like it would hard-code the logout link to use bananas, but I am wondering if I might be able to get a nudge on how to allow bananas and ondemand based on what server name/alias the client is trying to log out from.
Thank you!