Sameer, Cas should preserve the url, port, path, and parameters from the client. If not, you could use something like nginx as a proxy in front of your client application and cas.
Ray On Sat, 2023-02-18 at 22:40 -0800, Sameer Thajudin wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. I set up a CAS server locally so that I can test an application. Both the client application and CAS server runs on the same machine. The application redirects to the CAS server but the CAS server sees that the client IP address and the CAS server IP address is the same as shown below: CLIENT IP ADDRESS: 127.0.0.1 SERVER IP ADDRESS: 127.0.0.1 I believe this is the reason why when the CAS server redirects back after authentication, the base URL of the redirect URL is the URL of the CAS server(localhost and CAS server port). As both the client application and CAS server runs on the same machine on different ports, how can I ensure that the CAS server after authentication redirects to the client app url(localhost and client application port) rather than the CAS server? Thank you -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/76a483683b82077cae844cded6a55954786dd346.camel%40uvic.ca.
