It may help to read through the protocol specifications: http://www.jasig.org/cas/protocol
>From section 2.1.1: "service [OPTIONAL] - the identifier of the application the client is trying to access. In almost all cases, this will be the URL of the application. Note that as an HTTP request parameter, this URL value MUST be URL-encoded as described in Section 2.2 of RFC 1738[4<http://www.ja-sig.org/products/cas/protocol.html#4>]. If a service is not specified and a single sign-on session does not yet exist, CAS SHOULD request credentials from the user to initiate a single sign-on session. If a service is not specified and a single sign-on session already exists, CAS SHOULD display a message notifying the client that it is already logged in." >From section 2.1.2: "Simple login example: https://server/cas/login?service=http%3A%2F%2Fwww.service.com"; In the above example, the service parameter specifies the target application, where the user will be redirected following authentication. I think that will get you on the right track. Benjamin Mosior From: Richard Everett [mailto:[email protected]] Sent: Monday, December 16, 2013 8:38 AM To: [email protected] Subject: [cas-user] CAS "Login successful" page Hi all, When a user authenticates with our CAS instance they get directed to a CAS "Login Successful" page. Does CAS support configuration that would instead redirect the user to a page on our website? Apologies if this is covered in the manual. Kind regards, Richard -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
