Hi,
Nothing is obvious off the top of my head, but here's a few things to
consider/report back:
- Just to confirm, the server itself didn't change, just the application?
- Are the application files hosted locally or on a network share?
- Is the CAS dll in the application's bin directory or somewh
Can you give an example of what you mean with "various policies"?
The CAS service manager ships with the ability to explicitly deny
proxy capability to registered services. We make healthy use of this
feature at Virginia Tech. I'm sure I could invent additional policies
if pressed.
IIUC you co
Hi Marvin
Thanks very much for your explanation.
Can you give an example of what you mean with "various policies"?
I understand the concerns that the proxy client must be able to trust
the proxy chain, but if I maintain or rather am responsible for both
applications (proxy requestor and consu
On 05/07/13 15:44, Kapetanakis Giannis wrote:
>
> You are right. There was a trace in localhost log.
> It had to do with evaluationOrder in messages_en
>
> Thanks
>
However now I have a new error and I don't get any trace.
I can visit /cas/services/
but when I click "View Statistics" or "Manage S
On 05/07/13 15:18, Marvin S. Addison wrote:
I've recently upgraded to 3.5.2 (from 3.5.0) and having trouble
accessing the service management page.
I get "There was an error trying to complete your request. Please notify
your support desk or try again."
While trying to debug it I get these on the
The Service Ticket expiration timeout is configured at 10 seconds and as
you can see, the node 2 attemps to validate the ST in the same second so i
don't think it is a expiration problem.
Etienne.
Le vendredi 5 juillet 2013 14:31:43 UTC+2, Marvin S. Addison a écrit :
>
> > We have two nodes wh
In detail, we ran into a sign-out problem when the business
application is clustered behind a load balancer:
http://comments.gmane.org/gmane.comp.java.jasig.cas.devel/1495
Note we will ship rudimentary support for front-channel single sign-out
in CAS 4:
https://issues.jasig.org/browse/CAS-1292
We have two nodes who are running CAS server 3.5.1 and EhCache 2.6.
One node create the serviceTicket and the second node attemps to validate the
ST.
I can see in the logs that the second node receive the ST via RMI but
CentralAuthenticationServiceImpl said that the ST does not exist.
I see
and start to slowly understand how proxying works, but I still don't
understand why it has to be so complicated?
Andrew Petro is our resident expert on proxying, so I'm sure he could
provide a thoughtful answer. I'll take a shot, though, for what it's worth.
Why isn't it possible to forward
I've recently upgraded to 3.5.2 (from 3.5.0) and having trouble
accessing the service management page.
I get "There was an error trying to complete your request. Please notify
your support desk or try again."
While trying to debug it I get these on the cas.log
I see no error or stack trace. The
Hi,
Can someone comment on this?
regards,
Giannis
On 01/07/13 14:44, Kapetanakis Giannis wrote:
Hi,
I've recently upgraded to 3.5.2 (from 3.5.0) and having trouble
accessing the service management page.
I get "There was an error trying to complete your request. Please
notify your support d
11 matches
Mail list logo