Its not an issue with the Services Management Tool. Its an issue with what appears to be sent to CAS.
My guess is the way the app works, the request that is trigging the validation is the CSS file for some reason. On Tue, Jul 6, 2010 at 8:00 PM, Cary, Kim <[email protected]> wrote: > Yes, in the services management tool. Can we fix this issue at that level? > What, make it more specific? The specific URL is odd: > > https://wavenet.pepperdine.edu/psp/paprd89/?cmd=start > > On Jul 6, 2010, at 4:42 PM, Scott Battaglia wrote: > > > > > On Tue, Jul 6, 2010 at 1:09 PM, Cary, Kim <[email protected]> > wrote: > > Thanks! > > > > So, which service ID is from the browser and which the client > application? I'd like to tell the app devs to fix the issue... are they > adding or stripping the ?. > > > > WHEN REQUESTING TICKET: > https://wavenet.pepperdine.edu/psp/paprd89/css/cas.css > > VALIDATION: https://wavenet.pepperdine.edu/psp/paprd89/css/cas.css? > > > > > > Still wondering what happens for the customer? Does the client app get > told that the authentication is not successful in this case? > > > > It depends on the client. On the Java side, it would probably just mean > the CSS wasn't rendered. > > > > > > Yes, the higher level is protected at paprd89/** > > > > In the Services Management tool? > > > > Cheers, > > Scott > > > > > > > > On Jul 6, 2010, at 9:14 AM, Scott Battaglia wrote: > > > > > It means that for some reason a ticket was issued to a CSS file. When > that ticket was validated, the ids didn't match (the service authorization > is not involved here). > > > > > > Normally CSS files aren't protected OR the level above the CSS is > protected and the CSS files share in that session (such that they aren't > also issued an ST) > > > > > > > > > On Tue, Jul 6, 2010 at 12:09 PM, Cary, Kim <[email protected]> > wrote: > > > All, > > > > > > We got a few of these errors over the long weekend: > > > > > > > ServiceTicket [ST-70772-xxxxxxxxxxxxxxxxxxx-pcas] with service [ > https://wavenet.pepperdine.edu/psp/paprd89/css/cas.css does not match > supplied service [https://wavenet.pepperdine.edu/psp/paprd89/css/cas.css?] > > > > > > Can anyone confirm that this comes from the server checking the ticket > supplying a slightly different (but authorized) service from the service > supplied by the users browser when obtaining this ticket? > > > > > > What is the user experience when this happens? > > > - They are validated and admitted normally to the app? > > > - The client application gets a validation failure from the CAS server > and the user is rejected? > > > > > > KC > > > -- > > > 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 > > > > > > -- > > 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 > > > -- > 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
