Hi Milt, The default ticket registry (in-memory) is adequate for most (non-active/active clustered) installs. The only downside to the default ticket registry in your situation is that if you restart the containter (Tomcat/Jetty/etc) for any reason, the active tickets will be lost and users will have to re-authenticate. Most organizations tend to be OK with that.
John --- *John Gasper* IAM Consultant Unicon, Inc. PGP/GPG Key: 0xbafee3ef On 1/12/15 10:23 AM, Milt Epstein wrote: > This looks like a good place to ask this question. You mention that > to get CAS going, you need to configure an authentication handler, a > ticket registry, and a service registry. My question -- is the ticket > registry (other than the default ticket registry) required? Let me > add -- we don't have a clustered environment. > > I'm working on upgrading our CAS installation, and I have a test > version up and running, but I didn't set up anything for the ticket > registry. Our previous version didn't have anything for the ticket > registry either. I've looked through the documentation, and from what > I can tell, the ticket registry is not necessary unless you have a > clustered environment. But this isn't stated explicitly, so it would > be nice to verify. > > Thanks. > > Milt Epstein > Applications Developer > Graduate School of Library and Information Science (GSLIS) > University of Illinois at Urbana-Champaign (UIUC) > [email protected] > > > On Tue, 6 Jan 2015, John Gasper wrote: > >> Hi Douglas, >> >> I'd start by reviewing the docs [1]. You'll want to use the Maven WAR >> Overlay process [2] for generating your institution's specific build. In >> the instructions is a sample overlay to get you started. From there, >> commit (to a local [git or svn] repository) often as you make >> incremental config changes. You'll need to configure an authentication >> handler, a ticket registry, and a service registry. You'll want to study >> out the various options that you have. Not listed here, but very popular >> are additional registries [3]. The yaml services reg & the hazelcast >> ticket reg (if setting up a clustered environment) are the ones I'm >> speaking of specifically. >> >> [1] http://jasig.github.io/cas/4.0.x/index.html >> [2] >> http://jasig.github.io/cas/4.0.x/installation/Maven-Overlay-Installation.html >> [3] https://github.com/unicon-cas-addons >> >> Welcome to the club, and good luck! >> >> John >> >> --- >> *John Gasper* >> IAM Consultant >> Unicon, Inc. >> PGP/GPG Key: 0xbafee3ef >> On 1/6/15 4:47 AM, [email protected] wrote: >>> Hi, >>> >>> I deleted the old post and I am posting this again, for when I posted >>> it the first time, I got an email from wisclist that I was not on >>> their list cas-user. >>> I do not know the relation between the two lists, so I thought it >>> might be better to re-post this. Here is the previous post slightly >>> edited. >>> >>> --------------------------- >>> Hi, >>> >>> I have been tasked with learning about CAS and I wanted to test >>> installing it and getting familiar with it on a >>> Fedora VM. Where do I go to get started on learning about CAS and >>> installing it on a Fedora VM to test it out. >>> >>> Thanks, >>> Douglas >>> -- >>> 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
