Sorry for failing to reply on the mailinglist. (I just hit reply in my email client to the mailinglist email forgetting that doesn't go here.)
FYI The mixed bind and search came straight out of the docs for search: https://apereo.github.io/cas/development/installation/Configuration-Properties.html#database-authentication---search As for the authn static. The instructions are very straight forward, but I do not have anything with cas.authn.accept.users in my config file to remove. (The default CAS overlay also contains no "cas.authn.accept.users" and yet boots up with the default casuser/Mellon configuration so I'm assuming that somewhere in CAS casuser/Mellon is set as a default for authentication methods.) My overlay is here updated basically in full (I removed passwords, I'll change the signing keys later for production): https://github.com/loren138/cas-overlay-test I can try removing parts of my config file to see if that helps, but I've done my best to only define configuration for things we are actually going to use. Also, build run is still generating signing keys for some reason... I've done my best to define all the signing keys I can find in congifuration-properties for it so I'm not sure which key it is missing: 2016-08-04 14:16:35,750 WARN [org.apereo.cas.WebflowConversationStateCipherExecutor] - <Secret key for signing is not defined. CAS will attempt to auto-generate the signing key> 2016-08-04 14:16:35,810 WARN [org.apereo.cas.WebflowConversationStateCipherExecutor] - <Generated signing key C2P_HNAAWw3v0RjLiC88-fVPKM80SS0HVK12cjQ9iAsPX2Hj2BnDtpx3P_vFlVwoKyeqDHv5256QtarX-zfoJQ of size 512. The generated key MUST be added to CAS settings.> 2016-08-04 14:16:35,811 WARN [org.apereo.cas.WebflowConversationStateCipherExecutor] - <No encryption key is defined. CAS will attempt to auto-generate keys> 2016-08-04 14:16:35,813 WARN [org.apereo.cas.WebflowConversationStateCipherExecutor] - <Generated encryption key xsaIvfTfAazdnDvW of size 16. The generated key MUST be added to CAS settings.> Replies that missed the mailinglist: To clarify, your other issue with the error showing up is because CAS is having trouble reading and consuming the logging configuration file. It’s picking the wrong file, or it’s not allowed to read the file, etc. That’s why logs don’t show up. It doesn’t know how. You need to make sure everything is properly in /etc/cas/config by default, and readable by the running process. Fact that you can bring up CAS in embedded mode correctly shows that THAT process can read the file, but not the sudo-tomcat process. I leave the rest up to you. Also, pick your properties correctly. Last time I checked, you had some settings for bind, some for search, etc. None of that makes sense. If you don’t set the settings correctly, CAS won’t auto-configure them for you. It needs to know whether you are doing a search, a bind, or both. Nothing is partial. As for static authn, when you bring up CAS it should tell you something like this: CAS is configured to accept a static list of credentials for authentication. While this is generally useful for demo purposes, it is STRONGLY recommended that you DISABLE this authentication method (by REMOVING 'cas.authn.accept.users' from your configuration) and switch to a mode that is more suitable for production. I believe that’s pretty self explanatory. If you do what that line tells you to do, then static authn will switch off. If you have them configured settings correctly for JDBC authn, then those will kick into action. If you have done all of that and still something fails, LMK. I’ll need you overlay, plus full set of properties you have turned on and details on where you have defined them, etc. HTH. -- Misagh From: Misagh Moayyed Reply: Misagh Moayyed Date: August 4, 2016 at 10:05:18 AM To: Loren Subject: Re: [cas-user] CAS 5 Connect to JDBC for Authentication Remember to post to the mailing lists please. What do you mean by switching off static authn? What makes you think static authn is active? I don’t know what might cause your other error with your tomcat install. All I can tell you is that the log file is not read. If you are using a tomcat based on OS distros, don’t do that. -- Misagh From: Loren.Klingman Reply: Loren.Klingman Date: August 4, 2016 at 9:52:40 AM To: Misagh Moayyed Subject: Re: [cas-user] CAS 5 Connect to JDBC for Authentication Thanks, I added that and resolved an error about it not being able to find the SQL server jdbc driver, but I'm still getting only the static file auth on both build.sh run and my install on tomcat. Any other ideas? I'm also still getting the log error on tomcat but not on build.sh run. Where should the log files be bring saved from the tomcat version? I can check that directories permissions. I'm pretty sure it is reading the config file since i got the error about the jdbc driver. It just doesn't seem to be switching off static auth. Did I need to disable that somehow? On Wednesday, August 3, 2016 at 6:01:56 PM UTC-4, Misagh Moayyed wrote: > > Well, your other error about logs went away. So something’s up with > permissions and/or tomcat that reads them perhaps. > > If you want to get db authn working, it’s not enough to simply include the > properties. You’ll also need to declare the relevant module to express your > intention. Your overlay didnt show it. > > > https://apereo.github.io/cas/development/installation/Database-Authentication.html > > > -- > Misagh > > From: Loren Klingman <[email protected]> <javascript:> > Reply: Loren Klingman <[email protected]> <javascript:> > Date: August 3, 2016 at 2:36:22 PM > To: CAS Community <[email protected]> <javascript:> > Cc: [email protected] <javascript:> <[email protected]> <javascript:> > Subject: Re: [cas-user] CAS 5 Connect to JDBC for Authentication > > I still get the static login from ./bulid.sh run. It seems to generate a > bunch of keys which should have already been set in my cas.properties file > which leads me to think at least part of the problem is with that. > > The file is in /etc/cas/config/cas.properties (seems to be a new location > from the former /etc/cas/cas.properties). The file (and folders) are owned > by root:root, but the are all world readable. > > If nothing rings a bell in any of that, could you put the exact overlay > template you are using with database authentication online somewhere, and > I'll try pulling that in? (Of course, I'll have to change the database, > but even if I didn't if I can get to an error with the database connection > that would be progress.) > > Also, thanks so much for your help! I try to keep detailed notes so I'll > post my full install guide for Ubuntu 16.04 when I get it running and > hopefully that will help others. > > Here is my output: > __ ____ _ ____ __ > / / / ___| / \ / ___| \ \ > | | | | / _ \ \___ \ | | > | | | |___ / ___ \ ___) | | | > | | \____|/_/ \_\|____/ | | > \_\ /_/ > > CAS Version: 5.0.0.RC1-SNAPSHOT > Build Date/Time: 2016-08-03T21:18:38Z > Java Home: /usr/lib/jvm/java-8-openjdk-amd64/jre > Java Vendor: Oracle Corporation > Java Version: 1.8.0_91 > OS Architecture: amd64 > OS Name: Linux > OS Version: 4.4.0-21-generic > > > 2016-08-03 17:19:09,728 INFO [org.apereo.cas.web.CasWebApplication] - <The > following profiles are active: native> > 2016-08-03 17:20:17,567 INFO > [org.apereo.cas.services.DefaultServicesManagerImpl] - <Loaded 0 services > from InMemoryServiceRegistryDaoImpl.> > 2016-08-03 17:21:09,669 WARN > [org.apereo.cas.WebflowConversationStateCipherExecutor] - <Secret key for > signing is not defined. CAS will attempt to auto-generate the signing key> > 2016-08-03 17:21:09,738 WARN > [org.apereo.cas.WebflowConversationStateCipherExecutor] - <Generated > signing key > rIH_jLu8goRjqDI7nhatbyZiUGXHBcDxPmTQzPY9EoueP6ZicsQ77qnXkS1txOaDQinVQ7AWjBAV0leD9iE7TA > > of size 512. The generated key MUST be added to CAS settings.> > 2016-08-03 17:21:09,739 WARN > [org.apereo.cas.WebflowConversationStateCipherExecutor] - <No encryption > key is defined. CAS will attempt to auto-generate keys> > 2016-08-03 17:21:09,740 WARN > [org.apereo.cas.WebflowConversationStateCipherExecutor] - <Generated > encryption key YlXiwAUdrcsYlUjG of size 16. The generated key MUST be added > to CAS settings.> > 2016-08-03 17:21:10,808 WARN > [org.apereo.cas.config.CasSecurityContextConfiguration] - <> > 2016-08-03 17:21:10,825 WARN > [org.apereo.cas.config.CasSecurityContextConfiguration] - < > > ____ _____ ___ ____ _ > / ___| |_ _| / _ \ | _ \ | | > \___ \ | | | | | || |_) || | > ___) | | | | |_| || __/ |_| > |____/ |_| \___/ |_| (_) > > > CAS is configured to accept a static list of credentials for > authentication. While this is generally useful for demo purposes, it is > STRONGLY recommended that you DISABLE this authentication method (by > REMOVING 'cas.authn.accept.users' from your configuration) and switch to a > mode that is more suitable for production. > > > 2016-08-03 17:21:10,831 WARN > [org.apereo.cas.config.CasSecurityContextConfiguration] - <> > 2016-08-03 17:21:22,793 WARN > [org.apereo.cas.services.InMemoryServiceRegistryDaoImpl] - <Runtime memory > is used as the persistence storage for retrieving and persisting service > definitions. Changes that are made to service definitions during runtime > will be LOST upon container restarts.> > 2016-08-03 17:21:22,811 WARN > [org.apereo.cas.services.InMemoryServiceRegistryDaoImpl] - <Runtime memory > is used as the persistence storage for retrieving and persisting service > definitions. Changes that are made to service definitions during runtime > will be LOST upon container restarts.> > 2016-08-03 17:21:22,827 INFO > [org.apereo.cas.services.DefaultServicesManagerImpl] - <Loaded 2 services > from InMemoryServiceRegistryDaoImpl.> > 2016-08-03 17:22:04,182 INFO > [org.apereo.cas.configuration.CasConfigurationRebinder] - <Reloading CAS > configuration via > cas-org.apereo.cas.configuration.CasConfigurationProperties> > 2016-08-03 17:22:04,653 INFO > [org.apereo.cas.configuration.CasConfigurationRebinder] - <Reloaded CAS > configuration cas-org.apereo.cas.configuration.CasConfigurationProperties> > 2016-08-03 17:22:11,319 INFO [org.apereo.cas.web.CasWebApplication] - <The > following profiles are active: native> > 2016-08-03 17:22:12,953 INFO [org.apereo.cas.web.CasWebApplication] - > <Started CasWebApplication in 6.475 seconds (JVM running for 208.508)> > 2016-08-03 17:22:13,694 WARN > [org.apereo.cas.util.TicketGrantingCookieCipherExecutor] - <Secret key for > encryption is not defined. CAS will attempt to auto-generate the encryption > key> > 2016-08-03 17:22:13,695 WARN > [org.apereo.cas.util.TicketGrantingCookieCipherExecutor] - <Generated > encryption key ufXZRKBro-62lLFa79hlFrx94V2BTZHeRdpqY1iydgQ of size 256. The > generated key MUST be added to CAS settings.> > 2016-08-03 17:22:13,696 WARN > [org.apereo.cas.util.TicketGrantingCookieCipherExecutor] - <Secret key for > signing is not defined. CAS will attempt to auto-generate the signing key> > 2016-08-03 17:22:13,696 WARN > [org.apereo.cas.util.TicketGrantingCookieCipherExecutor] - <Generated > signing key > IeXJFidypAEpbWuUCpaEJh3c6Ghi9_eAhQs_6mUTFWUSmiVv137Fimp2HVdRVPnbT2HynF7gvJGbBYirLrON_w > > of size 512. The generated key MUST be added to CAS settings.> > 2016-08-03 17:22:14,152 INFO [org.apereo.cas.configuration.support.Beans] > - <Ticket registry encryption/signing is turned off. This may NOT be safe > in a clustered production environment. Consider using other choices to > handle encryption, signing and verification of ticket registry tickets.> > 2016-08-03 17:22:18,770 INFO [org.apereo.cas.web.CasWebApplication] - > <Started CasWebApplication in 207.005 seconds (JVM running for 214.325)> > 2016-08-03 17:22:27,505 INFO > [org.apereo.cas.web.support.InMemoryThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter] > > - <Beginning audit cleanup...> > 2016-08-03 17:22:37,505 INFO > [org.apereo.cas.services.DefaultServicesManagerImpl] - <Loaded 2 services > from InMemoryServiceRegistryDaoImpl.> > 2016-08-03 17:22:37,539 INFO > [org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <Beginning > ticket cleanup...> > 2016-08-03 17:22:37,546 INFO > [org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <0 expired > tickets removed.> > 2016-08-03 17:22:37,546 INFO > [org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <Finished > ticket cleanup.> > 2016-08-03 17:22:47,506 INFO > [org.apereo.cas.web.support.InMemoryThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter] > > - <Beginning audit cleanup...> > 2016-08-03 17:23:07,507 INFO > [org.apereo.cas.web.support.InMemoryThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter] > > - <Beginning audit cleanup...> > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - > expected >JDWP-Handshake< > 2016-08-03 17:23:27,507 INFO > [org.apereo.cas.web.support.InMemoryThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter] > > - <Beginning audit cleanup...> > 2016-08-03 17:23:37,505 INFO > [org.apereo.cas.services.DefaultServicesManagerImpl] - <Loaded 2 services > from InMemoryServiceRegistryDaoImpl.> > 2016-08-03 17:23:37,554 INFO > [org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <Beginning > ticket cleanup...> > 2016-08-03 17:23:37,555 INFO > [org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <0 expired > tickets removed.> > 2016-08-03 17:23:37,555 INFO > [org.apereo.cas.ticket.registry.DefaultTicketRegistryCleaner] - <Finished > ticket cleanup.> > 2016-08-03 17:23:43,749 INFO > [org.apereo.cas.web.flow.InitialFlowSetupAction] - <Setting path for > cookies for warn cookie generator to: /cas/ > > 2016-08-03 17:23:43,758 INFO > [org.apereo.cas.web.flow.InitialFlowSetupAction] - <Setting path for > cookies for TGC cookie generator to: /cas/ > > 2016-08-03 17:23:47,508 INFO > [org.apereo.cas.web.support.InMemoryThrottledSubmissionByIpAddressAndUsernameHandlerInterceptorAdapter] > > - <Beginning audit cleanup...> > 2016-08-03 17:23:57,560 INFO > [org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - > <AcceptUsersAuthenticationHandler failed authenticating lklingman112> > 2016-08-03 17:23:57,561 WARN > [org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - > <Authentication has failed. Credentials may be incorrect or CAS cannot find > authentication handler that supports [lklingman112] of type > [UsernamePasswordCredential], which suggests a configuration problem.> > 2016-08-03 17:23:57,576 INFO > [org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit > trail record BEGIN > > On Wednesday, August 3, 2016 at 4:56:35 PM UTC-4, Misagh Moayyed wrote: >> >> Cant duplicate. I’ll blame permissions, or tomcat. What happens when you >> run "./build.sh run”? >> >> -- >> Misagh >> >> From: Loren Klingman <[email protected]> >> Reply: Loren Klingman <[email protected]> >> Date: August 3, 2016 at 1:13:05 PM >> To: CAS Community <[email protected]> >> Cc: [email protected] <[email protected]> >> Subject: Re: [cas-user] CAS 5 Connect to JDBC for Authentication >> >> Reposting because I failed to post the last reply publically. >> >> Thanks, I've changed the cas.properties file as you requested. That line >> is actually exactly out of the overlay template on github ( >> https://github.com/apereo/cas-overlay-template/blob/5.0/etc/cas/config/cas.properties) >> >> so if it's wrong it probably needs to be updated there also. >> >> My log4j2.xml should be an exact copy from the 5.0 branch of the overlay >> template, but I'm attaching it here just in case I changed something by >> mistake. >> >> Since I don't want to push database passwords up, I did not push up any >> changes to cas.properties to the overlay (which means it's actually exactly >> the same as the master one) but for good measure and in case I need it for >> future testing, I did push up what I'm using (the 5.0 branch): >> https://github.com/loren138/cas-overlay-test >> >> For deployment, I'm using the following commands to build and then send >> the war file over to tomcat8: >> >> sudo ./build.sh package >> >> >> sudo service tomcat8 stop && sudo rm -rf /var/lib/tomcat8/webapps/ROOT && >> sudo cp ./target/cas.war /var/lib/tomcat8/webapps/ROOT.war && sudo service >> tomcat8 start >> >> >> >> >> Loren Klingman >> >> >> On Wednesday, August 3, 2016 at 3:40:49 PM UTC-4, Misagh Moayyed wrote: >>> >>> And, this: >>> >>> logging.config: file:/etc/cas/config/log4j2.xml >>> >>> >>> Probably should be: >>> >>> logging.config=file:/etc/cas/config/log4j2.xml >>> >>> >>> And you want to make sure that file exists. If it does, please share >>> that too. >>> >>> -- >>> Misagh >>> >>> From: Misagh Moayyed <[email protected]> >>> Reply: Misagh Moayyed <[email protected]> >>> Date: August 3, 2016 at 12:36:10 PM >>> To: CAS Community <[email protected]> >>> Subject: Re: [cas-user] CAS 5 Connect to JDBC for Authentication >>> >>> Got an overlay you can share? >>> >>> -- >>> Misagh >>> >>> From: Loren Klingman <[email protected]> >>> Reply: Loren Klingman <[email protected]> >>> Date: August 3, 2016 at 12:27:18 PM >>> To: CAS Community <[email protected]> >>> Subject: [cas-user] CAS 5 Connect to JDBC for Authentication >>> >>> I'm excited to start working with CAS 5 and setup all in the config >>> file, but I'm having issues getting switched over to auth in the database. >>> (IE casuser/Mellon is still the only login that works to login.) >>> >>> I've been trying to work slowly changing only what I need to at the time >>> so I don't think I've changed any other files other than cas.properties >>> (copied in below), but please let me know if some other file would be >>> useful to include. >>> >>> I'm seeing this error in catalina.out which may be related: >>> 2016-08-03 15:18:40,206 Log4j2-AsyncLoggerConfig-14 ERROR An exception >>> occurred processing Appender casAudit java.lang.NullPointerException >>> at org.apereo.cas.logging.CasAppender.append(CasAppender.java:85) >>> at >>> org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:155) >>> at >>> org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:128) >>> at >>> org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:119) >>> at >>> org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84) >>> at >>> org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:390) >>> at >>> org.apache.logging.log4j.core.async.AsyncLoggerConfig.asyncCallAppenders(AsyncLoggerConfig.java:113) >>> at >>> org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:111) >>> at >>> org.apache.logging.log4j.core.async.AsyncLoggerConfigDisruptor$Log4jEventWrapperHandler.onEvent(AsyncLoggerConfigDisruptor.java:97) >>> at >>> com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >>> at java.lang.Thread.run(Thread.java:745) >>> >>> I haven't found any CAS log files yet (looking in /var/log/cas where >>> they used to be) so let me know if I should be looking somewhere new for >>> those). >>> >>> Here is my cas.properties file: >>> >>> cas.server.name: https://webdev-g.sbts.edu >>> cas.server.prefix: https://webdev-g.sbts.edu/cas >>> >>> >>> cas.adminPagesSecurity.ip=(10)(\.(241|244|245|247|99))(\.([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0-9]|25[0-5])){2} >>> >>> # 8 hours - negative value = never expires >>> cas.ticket.tgt.maxTimeToLiveInSeconds=28800 >>> # 40 minutes (Set to a negative value to never expire tickets) >>> cas.ticket.tgt.timeToKillInSeconds=2400 >>> >>> ## >>> # CAS SSO Cookie Generation & Security >>> # See https://github.com/mitreid-connect/json-web-key-generator >>> # >>> # Do note that the following settings MUST be generated per deployment. >>> # >>> # Defaults at >>> spring-configuration/ticketGrantingTicketCookieGenerator.xml >>> # The encryption secret key. By default, must be a octet string of size >>> 256. >>> tgc.encryption.key=stuff... >>> # The signing secret key. By default, must be a octet string of size 512. >>> tgc.signing.key=stuf... >>> >>> ## >>> # Service Ticket Timeout >>> # Default sourced from >>> WEB-INF/spring-configuration/ticketExpirationPolices.xml >>> # >>> # Service Ticket timeout - typically kept short as a control against >>> replay attacks, default is 10s. You'll want to >>> # increase this timeout if you are manually testing service ticket >>> creation/validation via tamperdata or similar tools >>> cas.ticket.st.timeToKillInSeconds=45 >>> cas.ticket.st.numberOfUses=1 >>> >>> >>> cas.googleAnalytics.googleAnalyticsTrackingId=UA-801923423-2 >>> >>> cas.slo.disabled=true >>> # cas.slo.asynchronous=true >>> >>> logging.config: file:/etc/cas/config/log4j2.xml >>> >>> ## >>> # CAS Logout Behavior >>> # WEB-INF/cas-servlet.xml >>> # >>> # Specify whether CAS should redirect to the specified service parameter >>> on /logout requests >>> cas.logout.followServiceRedirects=true >>> # cas.serviceRegistry.config.location: classpath:/services >>> >>> # Authentication >>> >>> # Throttle - I honestly have no idea what units these things are in... >>> May the docs are better by now... >>> # >>> https://apereo.github.io/cas/development/installation/Configuration-Properties.html#authentication-throttling >>> cas.authn.throttle.usernameParameter=username >>> cas.authn.throttle.startDelay=10000 >>> cas.authn.throttle.repeatInterval=20000 >>> cas.authn.throttle.appcode=CAS >>> >>> cas.authn.throttle.failure.threshold=100 >>> cas.authn.throttle.failure.code=AUTHENTICATION_FAILED >>> cas.authn.throttle.failure.rangeSeconds=60 >>> >>> cas.authn.jdbc.search[0].fieldUser=username >>> cas.authn.jdbc.search[0].tableUsers=users >>> cas.authn.jdbc.search[0].fieldPassword=passwordsha1 >>> cas.authn.jdbc.search[0].healthQuery=SELECT 1 >>> cas.authn.jdbc.search[0].isolateInternalQueries=false >>> cas.authn.jdbc.search[0].url=jdbc:sqlserver://oeuoue;databaseName=qjkrcg >>> cas.authn.jdbc.search[0].failFast=true >>> cas.authn.jdbc.search[0].isolationLevelName=ISOLATION_READ_COMMITTED >>> >>> cas.authn.jdbc.search[0].dialect=org.hibernate.dialect.SQLServer2008Dialect >>> cas.authn.jdbc.search[0].leakThreshold=10 >>> cas.authn.jdbc.search[0].propagationBehaviorName=PROPAGATION_REQUIRED >>> cas.authn.jdbc.search[0].batchSize=1 >>> cas.authn.jdbc.search[0].user=CAS_User >>> cas.authn.jdbc.search[0].ddlAuto=validate >>> cas.authn.jdbc.search[0].maxAgeDays=180 >>> cas.authn.jdbc.search[0].password=ououeo >>> cas.authn.jdbc.search[0].autocommit=false >>> >>> cas.authn.jdbc.search[0].driverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver >>> cas.authn.jdbc.search[0].idleTimeout=5000 >>> >>> cas.authn.jdbc.search[0].passwordEncoder.type=STANDARD >>> cas.authn.jdbc.search[0].passwordEncoder.characterEncoding=UTF-8 >>> cas.authn.jdbc.search[0].passwordEncoder.encodingAlgorithm=SHA1 >>> cas.authn.jdbc.search[0].passwordEncoder.secret= >>> cas.authn.jdbc.search[0].passwordEncoder.strength=16 >>> >>> cas.authn.jdbc.bind[0].principalTransformation.suffix= >>> cas.authn.jdbc.bind[0].principalTransformation.caseConversion=LOWERCASE >>> cas.authn.jdbc.bind[0].principalTransformation.prefix= >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "CAS Community" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at >>> https://groups.google.com/a/apereo.org/group/cas-user/. >>> To view this discussion on the web visit >>> https://groups.google.com/a/apereo.org/d/msgid/cas-user/3179fbe9-67cc-4944-b8a1-e32519b7621e%40apereo.org >>> >>> <https://groups.google.com/a/apereo.org/d/msgid/cas-user/3179fbe9-67cc-4944-b8a1-e32519b7621e%40apereo.org?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/a/apereo.org/d/optout. >>> >>> -- > You received this message because you are subscribed to the Google Groups > "CAS Community" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To post to this group, send email to [email protected] <javascript:>. > Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/ > . > To view this discussion on the web visit > https://groups.google.com/a/apereo.org/d/msgid/cas-user/448e90ff-5edf-4c5b-a64e-afc6496f970e%40apereo.org > > <https://groups.google.com/a/apereo.org/d/msgid/cas-user/448e90ff-5edf-4c5b-a64e-afc6496f970e%40apereo.org?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/a/apereo.org/d/optout. > > -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/5253810b-3605-49ed-86dd-e1ff4a18b22d%40apereo.org. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
