Hi David!
We have CAS 4.0.0, also with Eh-Cache-based ticket registry, on a 4-node
cluster. Our configuration of EhCache is almost identical to yours.
Two weeks after our initial deployment, we started getting OOME too, on all
nodes. Our system admin measured heap consumption and the resulting
Another viable alternative would be to explore and consider Hazelcast Ticket
Registry:
https://github.com/Unicon/cas-addons/wiki/Configuring-HazelcastTicketRegistry
Best,
Dmitriy.
On Nov 18, 2014, at 06:40, Jaroslav Kacer jka...@idc.com wrote:
Hi David!
We have CAS 4.0.0, also with
That does seem to have corrected it.
Thanks,
Geoff
From: Jaroslav Kacer [mailto:jka...@idc.com]
Sent: Friday, November 07, 2014 8:47 AM
To: cas-user@lists.jasig.org
Subject: RE:[cas-user] EhCache Registry Exception
Hi Geoffrey!
Most likely it's because of missing parent=abstractTicketCache
Hello
Does the JSON plug-in from UNICON provide the same level of synchronization
across multiple servers that using a DB would?
Linda
--
Linda Toth
University of Alaska - Office of Information Technology (OIT) - Identity
and Access Management
910 Yukon Drive, Suite 103
Fairbanks, Alaska 99775
I'm setting up a new version of CAS, in anticipation of upgrading our
existing setup. I'm following the instructions on the website (i.e.,
https://jasig.github.io/cas/4.0.0/). A little background: Our
authentication is done via LDAP, and we also need to get some
attributes from LDAP. Some of
It does not. You would have to sync it some other way.
It would be handy if there was a hook to kick off an external program when
it writes out changes.
Since there are a few of us doing this and changes are rare we do it
manually.
-sent from my mobile
On Nov 18, 2014 2:54 PM, Linda Toth
Well, the hook is there (Spring Application Event representing the JSON file
resource change if it's property configured in the app ctx):
https://github.com/Unicon/cas-addons/blob/master/src/main/java/net/unicon/cas/addons/support/ResourceChangeDetectingEventNotifier.java#L39
So, I'd imagine
Hi, Milt:
Please make sure the attributes from LDAP is allowed, and not
filtered out from any filter.
util:list id=registeredServicesList
bean class=org.jasig.cas.services.RegexRegisteredService
... ... ...
!-- Comment out attributeFilter or change the
I didn't get any responses, but I believe I've figured out my issue.
The problem was that when I set up my ldapAuthenticationHandler, it
had a reference to a PrincipalResolver, so even though I had set up
the principalAttributeMap, it wasn't being used. This was in the bean
definition for
I encountered the same problems (null value, code snippet, ... etc.) before.
It really takes time to be familiar with CAS. But it's worth it.
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
On Tue, 18 Nov 2014 20:44:21 -0600 (CST)
Milt Epstein mepst...@illinois.edu wrote:
What led to this is that I had copied snippets of config from so many
places, and it wasn't clear what it all meant, how all the things
interacted.
Sounds familiar to me...
That's a problem with the
How to fix the Bcrypt password encoder
bean id=authenticationManager
class=org.jasig.cas.authentication.PolicyBasedAuthenticationManager
constructor-arg
map
entry key-ref=proxyAuthenticationHandler
value-ref=proxyPrincipalResolver /
entry
12 matches
Mail list logo
