Hi Guy, Sounds like you're conflating persisting the CAS ticket registry (a temporary cache of CAS-issued tickets) with persisting the service registry (configuration of which services CAS should allow to use CAS how).
You can choose to store the ticket registry into a database. I'd recommend the default registry implementation (in-memory) or the EhCache implementation instead. You can choose to store your service registry in a database. I'd suggest considering the JSON registry instead if you don't need write access through the web-based administrative UI. Yes, CAS service tickets are normally short-lived. Yes, service registrations will normally have empty entries in the rs_attributes (registered service attributes) table. In a simplest registration you'll specify zero attributes for CAS to release to the service. If you instead specify some, then they'll go in that table. I won't try to answer the locks table question since I'm not sure I'm up-to-date on how ticket registry cleaning works in the JPA ticket registry implementation. Again, I'd encourage the EhCache ticket registry instead if you need multi-node access to a shared ticket registry cache, and the Default implementation (in-memory) if you don't. Helps to reduce CAS's runtime dependency on the RDBMS. Hope this helps, Andrew On Thu, Oct 18, 2012 at 4:25 AM, Guy Thomas <[email protected]> wrote: > I set up a CAS server and two services. I added the persistence of the > registered services in an Oracle database. > > > > - I read somewhere that it’s normal that the serviceticket is so > short-lived (default: 10 seconds) that its registration in the serviceticket > table is also short-lived. Is this correct? > > - The locks table has this record: cas-ticket-registry-cleaner > (application_id, (null) (expiration_date), (null) (unique_id)). Is this OK? > > - The table rs_attributes remains empty: is this normal? What data > is supposed to be stored in this table? > > > > > > > > Guy Thomas > [snip] -- 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
