It turns out this is somehow related to a database table (LdapAttribute) that was removed from the prod database after I switched from the database registry to the JSON registry. The table was still in the test database, which is why it worked in test. Once I added this table back to the prod database everything started working normally. The strange part is that I added the table back without any data - the presence of the database is all that was needed.
I'm not sure if this LdapAttribute table is a customization in our setup or is part of the canned CAS installation (I inherited our CAS system from a former employee). -Adam On Mon, Jun 8, 2015 at 3:00 AM, Alberto Cabello Sánchez <albe...@unex.es> wrote: > On Fri, 05 Jun 2015 12:15:57 -0400 > Adam Causey <apcau...@vcu.edu> wrote: > > > This is for CAS 3.5.3. Yes, any service entries added via the web > > interface end up in the JSON file but not in the web interface. > > > > CAS does not authorize the websites that are added. > > Is the JSON file correct, or you can spot some apparent difference with the > testing one (which you said works fine)? > > -- > Alberto Cabello Sánchez > <albe...@unex.es> > -- You are currently subscribed to cas-user@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
