Morley,
It sounds like you could use the EhCacheTicketRegistry, which will persist tickets to disk. Simply don't configure the CacheManagerPeerProvider; you could add it later when you're ready for a clustered setup. My experience with CAS has so far only been with the JpaTicketRegistry backed by an Oracle database. It seems to me that it'd be relatively trivial in that setup to change the backend to anything for which a JDBC driver is available (e.g., SQLite). Best regards, -- Carlos. From: Morley Howell [mailto:[email protected]] Sent: Friday, 31 August, 2012 13:44 To: [email protected] Subject: RE: [cas-user] 3.5.0 release of cas-server-integration-berkeleydb? Thanks Dmitriy & Carlos. Is there a recommended/preferred persistent ticket registry implementation that works in both 3.4.7 and 3.5.0? Currently we need something as simple as possible, e.g. no need for clustering support, minimal/no runtime setup or maintenance, etc. Morley From: Dmitriy Kopylenko [mailto:[email protected]] Sent: August-31-12 11:35 AM To: [email protected] Subject: Re: [cas-user] 3.5.0 release of cas-server-integration-berkeleydb? This might be helpful: https://groups.google.com/forum/#!searchin/jasig-cas-user/berkeleydb/jasig -cas-user/bV7BPCIl3SY/VEXdWXev-68J Cheers, Dmitriy. On Fri, Aug 31, 2012 at 10:53 AM, Morley Howell <[email protected]> wrote: We're using the berkeleydb ticket registry under 3.4.7, but we're looking at upgrading to 3.5.0. The latest version of the cas-server-integration-berkeleydb module in maven central is 3.5.0-RC2. Will this version work with CAS 3.5.0? Any idea when a 3.5.0 version of the berkeleydb integration might be available? Thanks, Morley Howell This e-mail message is confidential, may be privileged and is intended for the exclusive use of the addressee. Any other person is strictly prohibited from disclosing, distributing or reproducing it. If the addressee cannot be reached or is unknown to you, please inform us immediately and delete this e-mail message and destroy all copies. Thank you. -- 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 This e-mail message is confidential, may be privileged and is intended for the exclusive use of the addressee. Any other person is strictly prohibited from disclosing, distributing or reproducing it. If the addressee cannot be reached or is unknown to you, please inform us immediately and delete this e-mail message and destroy all copies. Thank you. -- 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
