Also just to add, my controlservlet dosen't seem to execute either. Even if i add control servlet at the end by hand, I am not sure if this is because the key gets appended, but I think this is related to the callback not working as I expect?
On Mon, Mar 1, 2010 at 1:02 PM, Ravi <ravish.bhag...@gmail.com> wrote: > Hi All, > > I have got CAS up and running, it performs authentication as expected. But > I am pulling my hair out trying to fix one final issue. > > I fire up URL of my webapp 'k-authentify' as follows: > https://localhost:8443/k-authentify/controlservlet?cmd=test > > Since controlservlet is protected resource, I am redirected to CAS as for > login as expected. But URL looks like this: > https://localhost:8443/cas-server-webapp-3.3.5/login?service=https://localhost:8443/k-authentify > > So, although I accessed protected resource (controlservelt) using URL: > https://localhost:8443/k-authentify/controlservlet?cmd=test > > The ?service parameter says only upto https://localhost:8443/k-authentify! > > I thought it should use its Callback URL functionality to remember resource > being asked for? > > I am attaching my context and web.xml files, I will appreciate > helps/rebukes, I have been toiling for hours :( > -- > You are currently subscribed to cas-user@lists.jasig.org as: > ravish.bhag...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
