> This is odd, but you're correct, in all my logs there is no such > message. I've been authenticating fine for a long while when the > services list was just "http://**";.. CAS always knew I was logged in. > But maybe it needs to know the individual service too?
If CAS is not granting service tickets, you're not authenticating to the client service via CAS. Period. Sounds like a client misconfiguration problem. > I don't understand fully what I would need to change for that, since > CAS obviously knows about services (if I log in with a site not in the > services list, CAS tells me so and doesn't allow the login). That's because service authorization happens _before_ granting a service ticket. It's quite odd that you would get service checking without generating a ticket since both are keyed on the service attribute sent to the CAS /login URI. I'd check client configuration first in any case. M -- 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
