Hi all, i'm trying to test cas-server-3.5.2.1 on tomcat server so i've deployed the sample app war app. I changege the the cas.propreties entries according to my https://url:
server.name= server.prefix= cas.securityContext= I also add this entry to spring-configuration/securityContext.xml <sec:user-service id="userDetailsService"> <sec:user name="admin" password="admin" authorities="ROLE_ADMIN" /> </sec:user-service> but i can't access to https://serverlurl/mycas/services UsernameNotFoundException::admin what's wrong? Thanks in advance -----Messaggio originale----- Da: Andrew Morgan [mailto:mor...@orst.edu] Inviato: mercoledì 21 maggio 2014 17:43 A: cas-user@lists.jasig.org Oggetto: Re: [cas-user] Service Registry in database Heh, that's exactly what Marvin asked me last year. :) No, Inspektr is logging to an audit file. To make doubly sure, I even turned off auditing by commenting out the auditTrailManager bean and removing the auditTrailContext.xml file. Thanks, Andy On Tue, 20 May 2014, Scott Battaglia wrote: > Are you storing any auditing data in the database? > > > On Tue, May 20, 2014 at 7:03 PM, Andrew Morgan <mor...@orst.edu> wrote: > >> I'm reviving my old thread from last year because I need to perform >> some maintenance on MySQL and we cannot have our CAS instance be >> unavailable for the duration of the maintenance. >> >> I'm running CAS v3.5.2 with my ticket registry stored in memcache and >> my services registry stored in MySQL. When MySQL is down, submitting >> the CAS login form returns a "CAS is unavailable" error page from the CAS >> server. >> I have attached the stack trace that is dumped into catalina.out when >> this error occurs. >> >> I am simulating a MySQL outage with the following iptables rule: >> >> iptables -A INPUT -p tcp -i eth0 --dport 3306 -s 128.193.x.y -j >> REJECT --reject-with tcp-reset >> >> A packet capture of the traffic to the MySQL server shows that during >> a successful authentication (MySQL up), the following SQL commands >> are >> issued: >> >> SET autocommit=0 >> commit >> SET autocommit=1 >> SET autocommit=0 >> commit >> SET autocommit=1 >> >> When MySQL is down, the first "SET autocommit=0" is sent, which then >> causes the "CAS is unavailable" error. >> >> The stack trace indicates that some Spring AOP proxy is intercepting >> the call to createTicketGrantingTicket(). I see that >> createTicketGrantingTicket() has an @Transactional annotation applied >> to it. Could this be causing the spurious calls to autocommit and commit? >> >> I know a few people have reported this same issue, and other people >> have reported things working fine while MySQL is down. >> >> Is there any additional logging or testing I can do to narrow this down? >> >> Thanks, >> Andy >> -- >> You are currently subscribed to cas-user@lists.jasig.org as: >> scott.battag...@gmail.com >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-user >> > > -- > You are currently subscribed to cas-user@lists.jasig.org as: > mor...@orst.edu To unsubscribe, change settings or access archives, > see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to cas-user@lists.jasig.org as: alessandro.cu...@business-e.it To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- 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