What CAS client are you using? A CAS client should be encoding properly.
Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Leo Yamamoto <[email protected]> Date: Wed, 23 Feb 2011 14:26:31 To: <[email protected]> Reply-To: [email protected] Subject: [cas-user] Service URL encoding breaks parameters? I have CAS 3.4.6 configured and working correctly, but one issue I'm having is that since the service URL is encoded when redirected after a login, any parameters in the URL do not get properly interpreted by my client application. In my case, I have CAS integrated with Alfresco, a content management system. If I attempt to access an Alfresco web script (essentially a REST service), such as http://myhost/alfresco/wcs/api/myscript?key=value, then the CAS part works well and I can log in, but the redirect takes me to http://myhost/alfresco/wcs/api/myscript?key%3Dvalue, and the handler for "myscript" doesn't understand that there's a parameter named "key" with a value of "value." My question is, is this the expected behavior for CAS? I've searched around and found a lot of discussion in JIRA issues and such about having to escape things for security but it seems like with this behavior, any service URL that contains parameters would need to manually parse its query string. -- 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 -- 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
