RE: [cas-user] javax.persistence.TransactionRequiredException on CAS 4.1.1

2015-10-21 Thread Misagh Moayyed
Your overlay is pulling the wrong version for c3p0. That's why you get this 
error. Examine for duplicate dependencies, find where it's coming from and 
let us know. That would be the actual bug.

My bet is that it's coming from the webapp-support module.

> -Original Message-
> From: nico...@devels.es [mailto:nico...@devels.es]
> Sent: Wednesday, October 21, 2015 3:12 AM
> To: cas-user@lists.jasig.org
> Cc: Misagh Moayyed 
> Subject: RE: [cas-user] javax.persistence.TransactionRequiredException on 
> CAS
> 4.1.1
>
> Hi Misagh,
>
> I saw the document is already modified, so I replaced my existing
> configuration with the new one.
>
> Now I'm getting the following exception:
>
> oct 21, 2015 11:00:51 AM org.hibernate.dialect.Dialect 
> Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [
> acquireIncrement -> 16, acquireRetryAttempts -> 5, acquireRetryDelay ->
> 2000, autoCommitOnClose -> false, automaticTestTable -> null,
> breakAfterAcquireFailure -> false, checkoutTimeout -> 2000,
> connectionCustomizerClassName -> null, connectionTesterClassName ->
> com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName ->
> z8kfsx9c128vutd825zsr|25d663c8, debugUnreturnedConnectionStackTraces ->
> false, description -> null, driverClass -> com.mysql.jdbc.Driver,
> factoryClassLocation -> null, forceIgnoreUnresolvedTransactions ->
> false, identityToken -> z8kfsx9c128vutd825zsr|25d663c8,
> idleConnectionTestPeriod -> 30, initialPoolSize -> 6, jdbcUrl ->
> jdbc:mysql://fqdn:3306/cas?autoReconnect=true,
> lastAcquisitionFailureDefaultUser -> null, maxAdministrativeTaskTime ->
> 0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections
> -> 1000, maxPoolSize -> 18, maxStatements -> 0,
> maxStatementsPerConnection -> 0, minPoolSize -> 6, numHelperThreads ->
> 3, numThreadsAwaitingCheckoutDefaultUser -> 0, preferredTestQuery ->
> select 1, properties -> {user=**, password=**}, propertyCycle ->
> 0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false,
> unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies ->
> false ]
> oct 21, 2015 11:00:51 AM org.hibernate.dialect.Dialect 
> INFO: HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
> oct 21, 2015 11:00:51 AM
> org.hibernate.engine.jdbc.internal.LobCreatorBuilder
> useContextualLobCreation
> INFO: HHH000424: Disabling contextual LOB creation as createClob()
> method threw error : java.lang.reflect.InvocationTargetException
> oct 21, 2015 11:00:51 AM
> org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory 
> INFO: HHH000397: Using ASTQueryTranslatorFactory
> oct 21, 2015 11:00:51 AM org.hibernate.validator.internal.util.Version
> 
> INFO: HV01: Hibernate Validator 5.1.3.Final
> Hibernate: update RegisteredServiceImpl set access_strategy=?,
> attribute_release=?, description=?, evaluation_order=?, logo=?,
> logout_type=?, logout_url=?, name=?, proxy_policy=?, public_key=?,
> required_handlers=?, serviceId=?, theme=?, username_attr=? where id=?
> oct 21, 2015 11:00:53 AM
> org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl release
> INFO: HHH10: On release of batch it still contained JDBC statements
> [...]
> oct 21, 2015 11:01:12 AM
> org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl release
> INFO: HHH10: On release of batch it still contained JDBC statements
> 2015-10-21 11:01:12,943 WARN
> [org.springframework.web.context.support.XmlWebApplicationContext] -
>  refresh attempt
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'cas3ServiceSuccessView' defined in ServletContext
> resource [/WEB-INF/spring-configuration/protocolViewsConfiguration.xml]:
> Cannot resolve reference to bean 'casAttributeEncoder' while setting
> bean property 'casAttributeEncoder'; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'casAttributeEncoder' defined in ServletContext resource
> [/WEB-INF/spring-configuration/protocolViewsConfiguration.xml]: Cannot
> resolve reference to bean 'servicesManager' while setting constructor
> argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'servicesManager' defined in ServletContext resource
> [/WEB-INF/spring-configuration/applicationContext.xml]: Bean
> instantiation via constructor failed; nested exception is
> org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.jasig.cas.services.DefaultServicesManagerImpl]:
> Constructor threw exception; nested exception is
> java.lang.AbstractMethodError:
> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.setBinaryStream(ILjava/io/
> InputStream;J)V
>   at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolve
> Reference(BeanDefinitionValueResolver.java:359)
>   at
> 

[cas-user] Help with RegexRegisteredSevice - CAS 4.1.0

2015-10-21 Thread Dustin Lemp
I've been having a lot of problems getting CAS 4.1.0 set up.  I can log 
into CAS through LDAP just fine, but can't seem to get any services 
registered correctly. 

So far the closest I've gotten was with this config:

 {
  "@class" : "org.jasig.cas.services.RegexRegisteredService",
  "serviceId" : "https://CENSORED/FacultyGradeEntry/*;,
  "name" : "FacultyGradeEntry",
  "id" : 1003,
  "description" : "Faculty Grade Entry",
  "usernameAttributeProvider" : {
"@class" : 
"org.jasig.cas.services.PrincipalAttributeRegisteredServiceUsernameProvider",
"usernameAttribute" : "UDC_IDENTIFIER"
  },
"accessStrategy" : {
"@class" : 
"org.jasig.cas.services.DefaultRegisteredServiceAccessStrategy",
"enabled" : true,
"ssoEnabled" : true
  }

}



Services were easy to configure in the old version (3.5.2 I believe).  We 
just had to pop in something like:




https://CENSORED/FacultyGradeEntry/**; />



UDC_IDENTIFIER




into the deployerConfig and it all worked great.  The syntax for the new 
services is just so confusing.  Can anyone help me out, or point me in the 
direction of some documentation that can walk me through this?  Also, I 
have tried to set up the webapp for setting up services, but to no avail. 

Thanks!


-- 
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


[cas-user] SEVERE: Failed to initialize end point associated with ProtocolHandler ["http-bio-8080"] java.net.Bi

2015-10-21 Thread Jonas Steinberg
I thought that deploying my war locally would be a good baseline for testing.  
When I do, /tomcat7/logs/catalina.2015-10-21.log gives me the error:

SEVERE: Failed to initialize end point associated with ProtocolHandler 
["http-bio-8080"]
java.net.BindException: Address already in use :8080

I have verified via lsof and netstat that indeed no ther service are running on 
that port.

My tomcat/conf/server.xml configs are:



 

And my cas.properties configs are:

server.name=https://localhost:8080
server.prefix=${server.name}/cas
hz.cluster.members=localhost

Is there something obvious that I'm missing here?  I cannot reach 
https://localhost:8080/cas

If I remove my war I can reach https://localhost:8443 no problem.

I have tried messing with the ports, hostnames, etc. every way I can think of, 
but maybe I'm missing something.  I am very new to this.



-- 
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


RE: [cas-user] Help with RegexRegisteredSevice - CAS 4.1.0

2015-10-21 Thread Misagh Moayyed
See these please:

https://github.com/Jasig/cas/tree/4.1.x/cas-server-webapp/src/main/resources/services



There is an issue to update the docs to the new JSON format.



From: Dustin Lemp [mailto:dl...@jeffco.edu]
Sent: Wednesday, October 21, 2015 9:50 AM
To: cas-user@lists.jasig.org
Subject: [cas-user] Help with RegexRegisteredSevice - CAS 4.1.0



I've been having a lot of problems getting CAS 4.1.0 set up.  I can log into 
CAS through LDAP just fine, but can't seem to get any services registered 
correctly.



So far the closest I've gotten was with this config:



 {

  "@class" : "org.jasig.cas.services.RegexRegisteredService",

  "serviceId" : "https://CENSORED/FacultyGradeEntry/*;,

  "name" : "FacultyGradeEntry",

  "id" : 1003,

  "description" : "Faculty Grade Entry",

  "usernameAttributeProvider" : {

"@class" : 
"org.jasig.cas.services.PrincipalAttributeRegisteredServiceUsernameProvider",

"usernameAttribute" : "UDC_IDENTIFIER"

  },

"accessStrategy" : {

"@class" : 
"org.jasig.cas.services.DefaultRegisteredServiceAccessStrategy",

"enabled" : true,

"ssoEnabled" : true

  }



}






Services were easy to configure in the old version (3.5.2 I believe).  We 
just had to pop in something like:









https://CENSORED/FacultyGradeEntry/**; />





UDC_IDENTIFIER








into the deployerConfig and it all worked great.  The syntax for the new 
services is just so confusing.  Can anyone help me out, or point me in the 
direction of some documentation that can walk me through this?  Also, I have 
tried to set up the webapp for setting up services, but to no avail.



Thanks!




-- 
You are currently subscribed to cas-user@lists.jasig.org 
  as: mmoay...@unicon.net 

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


RE: [cas-user] javax.persistence.TransactionRequiredException on CAS 4.1.1

2015-10-21 Thread Misagh Moayyed
Could you try with c3p0 v0.9.5.1?

> -Original Message-
> From: Nicolás [mailto:nico...@devels.es]
> Sent: Wednesday, October 21, 2015 10:15 AM
> To: cas-user@lists.jasig.org
> Subject: Re: [cas-user] javax.persistence.TransactionRequiredException on 
> CAS
> 4.1.1
>
> I did a little research about this and it seems there are not any
> duplicate dependencies as far as I can tell.
>
> 1) For the cas webapp, we have the following dependencies:
>
>  
>  
>  org.jasig.cas
>  cas-server-webapp
>  ${cas.version}
>  war
>  runtime
>  
>  
>  org.jasig.cas
> cas-server-support-ldap
>  ${cas.version}
>  
>  
>org.jasig.cas
> cas-server-support-saml
>${cas.version}
>  
>  
>org.jasig.cas
> cas-server-support-jdbc
>${cas.version}
>runtime
>  
>  
>org.hibernate
>hibernate-core
>${hibernate.core.version}
>compile
>  
>  
>org.hibernate
> hibernate-entitymanager
>${hibernate.core.version}
>  
>  
>mysql
>mysql-connector-java
>${mysql.connector.version}
>  
>  
>org.jasig.cas
> cas-server-integration-hazelcast
>${cas.version}
>  
>  
>com.mchange
>c3p0
>${c3p0.version}
>  
>  
>
>  
>  4.1.1
> 4.3.10.Final
> 5.1.6
>  0.9.1.1
>  
>
>  When I list the /var/lib/tomcat7/webapps/cas/WEB-INF/lib directory,
> I find these:
>
>  -rw-r--r-- 1 tomcat7 tomcat7   62983 sep 22 09:39 activation-1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   11560 sep 22 21:14 
> annotations-1.3.2.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   74557 sep 22 09:39 
> annotations-2.0.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  445288 sep 22 09:39 antlr-2.7.7.jar
>  -rw-r--r-- 1 tomcat7 tomcat74467 sep 22 09:39 aopalliance-1.0.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  117529 sep 22 09:39 aspectjrt-1.8.6.jar
>  -rw-r--r-- 1 tomcat7 tomcat7 1862758 sep 22 09:39
> aspectjweaver-1.8.6.jar
>  -rw-r--r-- 1 tomcat7 tomcat7 2732684 nov  3  2014
> bcprov-jdk15on-1.50.jar
>  -rw-r--r-- 1 tomcat7 tomcat7 2842667 sep 22 09:39
> bcprov-jdk15on-1.51.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  608376 sep 22 09:39 c3p0-0.9.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   49789 sep 22 09:39 cache-api-1.0.0.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   63162 sep 22 09:39
> cache-ri-impl-1.0.0.jar
>  -rw-r--r-- 1 tomcat7 tomcat7 1943813 oct 20 07:44
> cas-server-core-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   90978 oct 20 07:43
> cas-server-core-api-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   29490 oct 20 07:43
> cas-server-integration-hazelcast-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   15872 ago 26 14:56
> cas-server-security-filter-2.0.3.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   46143 oct 19 13:43
> cas-server-support-generic-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   91082 oct 20 07:43
> cas-server-support-jdbc-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  127090 oct 20 07:43
> cas-server-support-ldap-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  249208 oct 20 07:43
> cas-server-support-saml-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  371643 oct 19 13:45
> cas-server-webapp-support-4.1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   52033 sep 22 09:39 cdi-api-1.0-SP4.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   60282 sep 22 09:39 classmate-1.0.0.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  232019 sep 22 09:39
> commons-beanutils-1.8.3.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  284184 sep 22 09:39
> commons-codec-1.10.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  575389 sep 22 09:39
> commons-collections-3.2.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  610259 sep 22 09:39
> commons-collections4-4.0.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   30595 sep 22 09:39
> commons-compiler-2.7.8.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  185140 sep 22 09:39 commons-io-2.4.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  132165 sep 22 09:39 
> commons-jexl-1.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  261809 sep 22 09:39 
> commons-lang-2.4.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  434678 sep 22 09:39 
> commons-lang3-3.4.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   62050 sep 22 09:39
> commons-logging-1.1.3.jar
>  -rw-r--r-- 1 tomcat7 tomcat7   61829 jun  5 14:04
> commons-logging-1.2.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  143710 sep 22 09:39 cryptacular-1.0.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  313898 sep 22 09:39 dom4j-1.6.1.jar
>  -rw-r--r-- 1 tomcat7 tomcat7  293863 sep 22 09:39
> FastInfoset-1.2.12.jar
>  -rw-r--r-- 1 tomcat7 tomcat7 1300487 sep 22 21:14 
> freemarker-2.3.22.jar
>  -rw-r--r-- 1 tomcat7 tomcat7 2256213 sep 22 09:39 guava-18.0.jar
>  -rw-r--r-- 1 

Re: [cas-user] Help with RegexRegisteredSevice - CAS 4.1.0

2015-10-21 Thread Dustin Lemp
Thanks for the reply!  I have looked over the sample services that are 
provided, but it's still very confusing on how to correctly register the 
services.  I guess I'll just wait until new documentation comes out on the 
new JSON format.

On Wednesday, October 21, 2015 at 1:48:52 PM UTC-5, Misagh Moayyed wrote:
>
> See these please: 
>
>
> https://github.com/Jasig/cas/tree/4.1.x/cas-server-webapp/src/main/resources/services
>
>  
>
> There is an issue to update the docs to the new JSON format. 
>
>
>

-- 
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


Re: [cas-user] javax.persistence.TransactionRequiredException on CAS 4.1.1

2015-10-21 Thread Nicolás
I did a little research about this and it seems there are not any 
duplicate dependencies as far as I can tell.


1) For the cas webapp, we have the following dependencies:



org.jasig.cas
cas-server-webapp
${cas.version}
war
runtime


org.jasig.cas
cas-server-support-ldap
${cas.version}


  org.jasig.cas
cas-server-support-saml
  ${cas.version}


  org.jasig.cas
cas-server-support-jdbc
  ${cas.version}
  runtime


  org.hibernate
  hibernate-core
  ${hibernate.core.version}
  compile


  org.hibernate
hibernate-entitymanager
  ${hibernate.core.version}


  mysql
  mysql-connector-java
  ${mysql.connector.version}


  org.jasig.cas
cas-server-integration-hazelcast
  ${cas.version}


  com.mchange
  c3p0
  ${c3p0.version}




4.1.1
4.3.10.Final
5.1.6
0.9.1.1


When I list the /var/lib/tomcat7/webapps/cas/WEB-INF/lib directory, 
I find these:


-rw-r--r-- 1 tomcat7 tomcat7   62983 sep 22 09:39 activation-1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7   11560 sep 22 21:14 annotations-1.3.2.jar
-rw-r--r-- 1 tomcat7 tomcat7   74557 sep 22 09:39 annotations-2.0.1.jar
-rw-r--r-- 1 tomcat7 tomcat7  445288 sep 22 09:39 antlr-2.7.7.jar
-rw-r--r-- 1 tomcat7 tomcat74467 sep 22 09:39 aopalliance-1.0.jar
-rw-r--r-- 1 tomcat7 tomcat7  117529 sep 22 09:39 aspectjrt-1.8.6.jar
-rw-r--r-- 1 tomcat7 tomcat7 1862758 sep 22 09:39 
aspectjweaver-1.8.6.jar
-rw-r--r-- 1 tomcat7 tomcat7 2732684 nov  3  2014 
bcprov-jdk15on-1.50.jar
-rw-r--r-- 1 tomcat7 tomcat7 2842667 sep 22 09:39 
bcprov-jdk15on-1.51.jar

-rw-r--r-- 1 tomcat7 tomcat7  608376 sep 22 09:39 c3p0-0.9.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7   49789 sep 22 09:39 cache-api-1.0.0.jar
-rw-r--r-- 1 tomcat7 tomcat7   63162 sep 22 09:39 
cache-ri-impl-1.0.0.jar
-rw-r--r-- 1 tomcat7 tomcat7 1943813 oct 20 07:44 
cas-server-core-4.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7   90978 oct 20 07:43 
cas-server-core-api-4.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7   29490 oct 20 07:43 
cas-server-integration-hazelcast-4.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7   15872 ago 26 14:56 
cas-server-security-filter-2.0.3.jar
-rw-r--r-- 1 tomcat7 tomcat7   46143 oct 19 13:43 
cas-server-support-generic-4.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7   91082 oct 20 07:43 
cas-server-support-jdbc-4.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7  127090 oct 20 07:43 
cas-server-support-ldap-4.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7  249208 oct 20 07:43 
cas-server-support-saml-4.1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7  371643 oct 19 13:45 
cas-server-webapp-support-4.1.1.jar

-rw-r--r-- 1 tomcat7 tomcat7   52033 sep 22 09:39 cdi-api-1.0-SP4.jar
-rw-r--r-- 1 tomcat7 tomcat7   60282 sep 22 09:39 classmate-1.0.0.jar
-rw-r--r-- 1 tomcat7 tomcat7  232019 sep 22 09:39 
commons-beanutils-1.8.3.jar
-rw-r--r-- 1 tomcat7 tomcat7  284184 sep 22 09:39 
commons-codec-1.10.jar
-rw-r--r-- 1 tomcat7 tomcat7  575389 sep 22 09:39 
commons-collections-3.2.1.jar
-rw-r--r-- 1 tomcat7 tomcat7  610259 sep 22 09:39 
commons-collections4-4.0.jar
-rw-r--r-- 1 tomcat7 tomcat7   30595 sep 22 09:39 
commons-compiler-2.7.8.jar

-rw-r--r-- 1 tomcat7 tomcat7  185140 sep 22 09:39 commons-io-2.4.jar
-rw-r--r-- 1 tomcat7 tomcat7  132165 sep 22 09:39 commons-jexl-1.1.jar
-rw-r--r-- 1 tomcat7 tomcat7  261809 sep 22 09:39 commons-lang-2.4.jar
-rw-r--r-- 1 tomcat7 tomcat7  434678 sep 22 09:39 commons-lang3-3.4.jar
-rw-r--r-- 1 tomcat7 tomcat7   62050 sep 22 09:39 
commons-logging-1.1.3.jar
-rw-r--r-- 1 tomcat7 tomcat7   61829 jun  5 14:04 
commons-logging-1.2.jar

-rw-r--r-- 1 tomcat7 tomcat7  143710 sep 22 09:39 cryptacular-1.0.jar
-rw-r--r-- 1 tomcat7 tomcat7  313898 sep 22 09:39 dom4j-1.6.1.jar
-rw-r--r-- 1 tomcat7 tomcat7  293863 sep 22 09:39 
FastInfoset-1.2.12.jar

-rw-r--r-- 1 tomcat7 tomcat7 1300487 sep 22 21:14 freemarker-2.3.22.jar
-rw-r--r-- 1 tomcat7 tomcat7 2256213 sep 22 09:39 guava-18.0.jar
-rw-r--r-- 1 tomcat7 tomcat7 6585052 sep 22 21:14 hazelcast-3.5.jar
-rw-r--r-- 1 tomcat7 tomcat7   33023 sep 22 21:14 
hazelcast-code-generator-3.5.jar
-rw-r--r-- 1 tomcat7 tomcat7   75324 sep 22 09:39 
hibernate-commons-annotations-4.0.5.Final.jar
-rw-r--r-- 1 tomcat7 tomcat7 5280098 sep 22 09:39 
hibernate-core-4.3.10.Final.jar
-rw-r--r-- 1 tomcat7 tomcat7  647704 sep 22 09:39 
hibernate-entitymanager-4.3.10.Final.jar
-rw-r--r-- 1 tomcat7 tomcat7  113371 sep 22 09:39 
hibernate-jpa-2.1-api-1.0.0.Final.jar
-rw-r--r-- 1 tomcat7 tomcat7  634265 sep 22 09:39 

[cas-user] FileMaker Pro and CAS

2015-10-21 Thread Joel Levin
Hi All:

Has anyone integrated FileMaker Pro with CAS?

A Google search did not come up with anything - hoping that someone has
previously and for any tips on steps to take.

Thanks.

-- 
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


Re: [cas-user] utterly lost on cas 4.1.0 Saw '301 Moved Permanently' error

2015-10-21 Thread Jonas Steinberg
I'll build and deploy this immediately when I get to work.
On Oct 21, 2015 4:46 AM, "Dmitriy Kopylenko"  wrote:

> All right. Let's try this one last time:
>
> 1) With fresh overlay for version of CAS 4.1.0, just include the Hazelcast
> module in your pom, as described in the documentation.
>
> 2) There is no need to include a deployerConfigContext.xml if you are just
> fine with the default provided by published CAS' war
>
> 3) IMPORTANT: Do NOT bring the ticketRegistry.xml config from cas-addons
> project as this WILL NOT work. That particular addon is built for CAS v3
> and is incompatible with Hazelcast ticket registry config included in CAS
> version 4.1.0
>
> Now you have Hazelcast ticket registry enabled in your CAS server (even
> though you are seeing the default ticketRegistry.xml in your war. That
> config is OVERWRITTEN by the Hazelcast ticket registry config contained in
> the included jar)
>
> I hope that this is clear enough.
>
> Best of luck.
>
> D.
>
> Sent from my iPhone
>
> On Oct 20, 2015, at 19:38, Jonas Steinberg 
> wrote:
>
> Ok, fair enough.  Except...
>
> I've been through this so much now Dmitriy that I've got a very fresh
> overlay going.  Let me show you some output from my currently running
> tomcat7 instance, which will show you that in some sense hazelcast is
> running:
>
>
> Oct 20, 2015 5:26:13 PM org.hibernate.validator.internal.util.Version
> 
> INFO: HV01: Hibernate Validator 5.1.3.Final
> 2015-10-20 17:26:28,360 INFO
> [org.jasig.cas.ticket.registry.HazelcastTicketRegistry]
> 
> 2015-10-20 17:26:43,366 INFO
> [org.jasig.cas.util.AutowiringSchedulerFactoryBean] -  Scheduler now>
> 2015-10-20 17:26:43,371 INFO [org.jasig.cas.CasEnvironmentContextListener]
> - <[Apache Tomcat/7.0.23] has loaded the CAS application context>
> 2015-10-20 17:26:52,492 INFO
> [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
> 
> 2015-10-20 17:26:53,181 INFO
> [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - <0
> expired tickets found to be removed.>
> 2015-10-20 17:26:53,215 INFO
> [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] -
> 
> Oct 20, 2015 5:26:59 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory /usr/local/tomcat7/webapps/ROOT
> Oct 20, 2015 5:26:59 PM org.apache.catalina.startup.HostConfig
> deployDirectory
> INFO: Deploying web application directory
> /usr/local/tomcat7/webapps/host-manager
> Oct 20, 2015 5:26:59 PM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-bio-7087"]
> Oct 20, 2015 5:26:59 PM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-bio-7086"]
> Oct 20, 2015 5:26:59 PM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-bio-7473"]
> Oct 20, 2015 5:26:59 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 120112 ms
> 2015-10-20 17:28:35,761 INFO
> [org.jasig.cas.services.DefaultServicesManagerImpl] -  services.>
> 2015-10-20 17:28:35,781 INFO
> [org.jasig.cas.services.DefaultServicesManagerImpl] - 
> 2015-10-20 17:30:35,761 INFO
> [org.jasig.cas.services.DefaultServicesManagerImpl] -  services.>
> 2015-10-20 17:30:35,782 INFO
> [org.jasig.cas.services.DefaultServicesManagerImpl] - 
> 2015-10-20 17:32:35,760 INFO
> [org.jasig.cas.services.DefaultServicesManagerImpl] -  service
>
>
>
> This is right out of tomcat7.
>
> However, using this deployConfigContext.xml file that you recommended:
>
>
> https://github.com/Jasig/cas/blob/v4.1.0/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml#L109
>
> ...definitely results in the default ticketRegistry being written.
>
> Now, I would inject this in there:
>
>
> https://github.com/Unicon/cas-addons/wiki/Configuring-HazelcastTicketRegistry
>
> Except that throws errors.
>
> So...do I need to do filtering or whatever or what?  Because that hz
> ticket registry is not being written in there...
>
>
> On Tue, Oct 20, 2015 at 5:28 PM, Dmitriy Kopylenko 
> wrote:
>
>> By merely including the Hazelcast ticket registry module dependency, it
>> should override the default ticket registry config which is read from HZ
>> module jar. The default CAS' web.xml has that config bit turned on.
>>
>> I'd suggest you start from a fresh overlay project and follow the 4.1
>> documentation to turn the HZ ticket registry on.
>>
>> Best,
>> D.
>>
>>
>>
>> Sent from my iPhone
>>
>> On Oct 20, 2015, at 19:08, Jonas Steinberg 
>> wrote:
>>
>> Yep.  There's definitely something wrong with using
>> https://github.com/Jasig/cas/blob/v4.1.0/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml
>> because now in target/cas/WEB-INF/spring-configuration my
>> ticketRegistry.xml is the default registry and not the hazelcast registry.
>> Any thoughts?
>>
>> On Tue, Oct 20, 2015 at 5:06 PM, Jonas 

RE: [cas-user] javax.persistence.TransactionRequiredException on CAS 4.1.1

2015-10-21 Thread nicolas

Hi Misagh,

I saw the document is already modified, so I replaced my existing 
configuration with the new one.


Now I'm getting the following exception:

oct 21, 2015 11:00:51 AM org.hibernate.dialect.Dialect 
Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ 
acquireIncrement -> 16, acquireRetryAttempts -> 5, acquireRetryDelay -> 
2000, autoCommitOnClose -> false, automaticTestTable -> null, 
breakAfterAcquireFailure -> false, checkoutTimeout -> 2000, 
connectionCustomizerClassName -> null, connectionTesterClassName -> 
com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceName -> 
z8kfsx9c128vutd825zsr|25d663c8, debugUnreturnedConnectionStackTraces -> 
false, description -> null, driverClass -> com.mysql.jdbc.Driver, 
factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> 
false, identityToken -> z8kfsx9c128vutd825zsr|25d663c8, 
idleConnectionTestPeriod -> 30, initialPoolSize -> 6, jdbcUrl -> 
jdbc:mysql://fqdn:3306/cas?autoReconnect=true, 
lastAcquisitionFailureDefaultUser -> null, maxAdministrativeTaskTime -> 
0, maxConnectionAge -> 0, maxIdleTime -> 0, maxIdleTimeExcessConnections 
-> 1000, maxPoolSize -> 18, maxStatements -> 0, 
maxStatementsPerConnection -> 0, minPoolSize -> 6, numHelperThreads -> 
3, numThreadsAwaitingCheckoutDefaultUser -> 0, preferredTestQuery -> 
select 1, properties -> {user=**, password=**}, propertyCycle -> 
0, testConnectionOnCheckin -> false, testConnectionOnCheckout -> false, 
unreturnedConnectionTimeout -> 0, usesTraditionalReflectiveProxies -> 
false ]

oct 21, 2015 11:00:51 AM org.hibernate.dialect.Dialect 
INFO: HHH000400: Using dialect: org.hibernate.dialect.MySQLDialect
oct 21, 2015 11:00:51 AM 
org.hibernate.engine.jdbc.internal.LobCreatorBuilder 
useContextualLobCreation
INFO: HHH000424: Disabling contextual LOB creation as createClob() 
method threw error : java.lang.reflect.InvocationTargetException
oct 21, 2015 11:00:51 AM 
org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory 

INFO: HHH000397: Using ASTQueryTranslatorFactory
oct 21, 2015 11:00:51 AM org.hibernate.validator.internal.util.Version 


INFO: HV01: Hibernate Validator 5.1.3.Final
Hibernate: update RegisteredServiceImpl set access_strategy=?, 
attribute_release=?, description=?, evaluation_order=?, logo=?, 
logout_type=?, logout_url=?, name=?, proxy_policy=?, public_key=?, 
required_handlers=?, serviceId=?, theme=?, username_attr=? where id=?
oct 21, 2015 11:00:53 AM 
org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl release

INFO: HHH10: On release of batch it still contained JDBC statements
[...]
oct 21, 2015 11:01:12 AM 
org.hibernate.engine.jdbc.batch.internal.AbstractBatchImpl release

INFO: HHH10: On release of batch it still contained JDBC statements
2015-10-21 11:01:12,943 WARN 
[org.springframework.web.context.support.XmlWebApplicationContext] - 
refresh attempt
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'cas3ServiceSuccessView' defined in ServletContext 
resource [/WEB-INF/spring-configuration/protocolViewsConfiguration.xml]: 
Cannot resolve reference to bean 'casAttributeEncoder' while setting 
bean property 'casAttributeEncoder'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'casAttributeEncoder' defined in ServletContext resource 
[/WEB-INF/spring-configuration/protocolViewsConfiguration.xml]: Cannot 
resolve reference to bean 'servicesManager' while setting constructor 
argument; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating 
bean with name 'servicesManager' defined in ServletContext resource 
[/WEB-INF/spring-configuration/applicationContext.xml]: Bean 
instantiation via constructor failed; nested exception is 
org.springframework.beans.BeanInstantiationException: Failed to 
instantiate [org.jasig.cas.services.DefaultServicesManagerImpl]: 
Constructor threw exception; nested exception is 
java.lang.AbstractMethodError: 
com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.setBinaryStream(ILjava/io/InputStream;J)V
	at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:359)
	at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:108)
	at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1477)
	at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1222)
	at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:537)
	at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:476)
	at 

Re: [cas-user] utterly lost on cas 4.1.0 Saw '301 Moved Permanently' error

2015-10-21 Thread Dmitriy Kopylenko
All right. Let's try this one last time:

1) With fresh overlay for version of CAS 4.1.0, just include the Hazelcast 
module in your pom, as described in the documentation. 

2) There is no need to include a deployerConfigContext.xml if you are just fine 
with the default provided by published CAS' war

3) IMPORTANT: Do NOT bring the ticketRegistry.xml config from cas-addons 
project as this WILL NOT work. That particular addon is built for CAS v3 and is 
incompatible with Hazelcast ticket registry config included in CAS version 4.1.0

Now you have Hazelcast ticket registry enabled in your CAS server (even though 
you are seeing the default ticketRegistry.xml in your war. That config is 
OVERWRITTEN by the Hazelcast ticket registry config contained in the included 
jar)

I hope that this is clear enough. 

Best of luck. 

D.  

Sent from my iPhone

> On Oct 20, 2015, at 19:38, Jonas Steinberg  wrote:
> 
> Ok, fair enough.  Except...
> 
> I've been through this so much now Dmitriy that I've got a very fresh overlay 
> going.  Let me show you some output from my currently running tomcat7 
> instance, which will show you that in some sense hazelcast is running:
> 
> 
> Oct 20, 2015 5:26:13 PM org.hibernate.validator.internal.util.Version 
> INFO: HV01: Hibernate Validator 5.1.3.Final
> 2015-10-20 17:26:28,360 INFO 
> [org.jasig.cas.ticket.registry.HazelcastTicketRegistry]
> 
> 2015-10-20 17:26:43,366 INFO 
> [org.jasig.cas.util.AutowiringSchedulerFactoryBean] -  Scheduler now>
> 2015-10-20 17:26:43,371 INFO [org.jasig.cas.CasEnvironmentContextListener] - 
> <[Apache Tomcat/7.0.23] has loaded the CAS application context>
> 2015-10-20 17:26:52,492 INFO 
> [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - 
> 
> 2015-10-20 17:26:53,181 INFO 
> [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - <0 
> expired tickets found to be removed.>
> 2015-10-20 17:26:53,215 INFO 
> [org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - 
> 
> Oct 20, 2015 5:26:59 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory /usr/local/tomcat7/webapps/ROOT
> Oct 20, 2015 5:26:59 PM org.apache.catalina.startup.HostConfig deployDirectory
> INFO: Deploying web application directory 
> /usr/local/tomcat7/webapps/host-manager
> Oct 20, 2015 5:26:59 PM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-bio-7087"]
> Oct 20, 2015 5:26:59 PM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-bio-7086"]
> Oct 20, 2015 5:26:59 PM org.apache.coyote.AbstractProtocol start
> INFO: Starting ProtocolHandler ["http-bio-7473"]
> Oct 20, 2015 5:26:59 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 120112 ms
> 2015-10-20 17:28:35,761 INFO 
> [org.jasig.cas.services.DefaultServicesManagerImpl] -  services.>
> 2015-10-20 17:28:35,781 INFO 
> [org.jasig.cas.services.DefaultServicesManagerImpl] - 
> 2015-10-20 17:30:35,761 INFO 
> [org.jasig.cas.services.DefaultServicesManagerImpl] -  services.>
> 2015-10-20 17:30:35,782 INFO 
> [org.jasig.cas.services.DefaultServicesManagerImpl] - 
> 2015-10-20 17:32:35,760 INFO 
> [org.jasig.cas.services.DefaultServicesManagerImpl] -  service
> 
> 
> 
> This is right out of tomcat7.
> 
> However, using this deployConfigContext.xml file that you recommended:
> 
> https://github.com/Jasig/cas/blob/v4.1.0/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml#L109
> 
> ...definitely results in the default ticketRegistry being written.  
> 
> Now, I would inject this in there:
> 
> https://github.com/Unicon/cas-addons/wiki/Configuring-HazelcastTicketRegistry
> 
> Except that throws errors.
> 
> So...do I need to do filtering or whatever or what?  Because that hz ticket 
> registry is not being written in there...
> 
> 
>> On Tue, Oct 20, 2015 at 5:28 PM, Dmitriy Kopylenko  
>> wrote:
>> By merely including the Hazelcast ticket registry module dependency, it 
>> should override the default ticket registry config which is read from HZ 
>> module jar. The default CAS' web.xml has that config bit turned on. 
>> 
>> I'd suggest you start from a fresh overlay project and follow the 4.1 
>> documentation to turn the HZ ticket registry on.
>> 
>> Best,
>> D. 
>> 
>> 
>> 
>> Sent from my iPhone
>> 
>>> On Oct 20, 2015, at 19:08, Jonas Steinberg  
>>> wrote:
>>> 
>>> Yep.  There's definitely something wrong with using 
>>> https://github.com/Jasig/cas/blob/v4.1.0/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml
>>>  because now in target/cas/WEB-INF/spring-configuration my 
>>> ticketRegistry.xml is the default registry and not the hazelcast registry.  
>>> Any thoughts?
>>> 
 On Tue, Oct 20, 2015 at 5:06 PM, Jonas Steinberg 
  wrote:
 I think my problem is this:
 
 I'm using this:
 
 

[cas-user] Error 500 when validating SAML

2015-10-21 Thread Pau I . Gómez Molina
Good morning,

We are trying to activate SAML validation but it doesn't work. We have followed 
documentation for 4.0.X version.

This is the LOG after trying authenticate:

2015-10-21 12:30:53,831 DEBUG 
[org.jasig.cas.authentication.LdapAuthenticationHandler] - Attempting LDAP 
authentication for +password - (certificate:)
2015-10-21 12:30:53,863 INFO [org.ldaptive.auth.Authenticator] - Authentication 
succeeded for dn: uid=,o=,c=XX
2015-10-21 12:30:53,863 DEBUG 
[org.jasig.cas.authentication.LdapAuthenticationHandler] - LDAP response: 
[org.ldaptive.auth.AuthenticationResponse@5290428::authenticationResultCode=AUTHENTICATION_HANDLER_SUCCESS,
 ldapEntry=[dn=uid=,o=,c=XX[[uid[]], [givenName[]], [sn[]], 
[isMemberOf[cn=,ou=XXX,o=, o=,c=, uid=,o=,c=XX, 
cn=,o=,o=,c=XX]]], responseControls=null, messageId=-1], 
accountState=null, result=true, resultCode=SUCCESS, message=null, controls=null]
2015-10-21 12:30:53,864 DEBUG 
[org.jasig.cas.authentication.LdapAuthenticationHandler] - Found principal 
attribute: [isMemberOf[cn=,ou=,o=,o=,c=XX, 
uid=,o=,c=XX, cn=,o=,o=,c=XX]]
2015-10-21 12:30:53,865 DEBUG 
[org.jasig.cas.authentication.LdapAuthenticationHandler] - Found principal 
attribute: [givenName[]]
2015-10-21 12:30:53,865 DEBUG 
[org.jasig.cas.authentication.LdapAuthenticationHandler] - Found principal 
attribute: [sn[]]
2015-10-21 12:30:53,865 INFO 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - 
LdapAuthenticationHandler successfully authenticated +password - 
(certificate:)
2015-10-21 12:30:53,866 DEBUG 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - Resolver is 
null.
2015-10-21 12:30:53,866 DEBUG 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - No resolver 
configured for LdapAuthenticationHandler. Falling back to handler principal 
2015-10-21 12:30:53,866 DEBUG 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - Principal=
2015-10-21 12:30:53,866 DEBUG 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - Setting 
principal.
2015-10-21 12:30:53,866 DEBUG 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - Returning 
builder.
2015-10-21 12:30:53,867 INFO 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - Authenticated 
 with credentials [+password - (certificate:)].
2015-10-21 12:30:53,869 DEBUG 
[org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - Attribute map 
for : {isMemberOf=[cn=,ou=,o=,o=,c=XX, uid=,c=XX, 
cn=,o=,o=,c=XX], givenName=, sn=}
2015-10-21 12:30:53,884 INFO 
[com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - Audit trail 
record BEGIN
=
WHO: audit:unknown
WHAT: supplied credentials: [+password - (certificate:)]
ACTION: AUTHENTICATION_SUCCESS
APPLICATION: SSO
WHEN: Wed Oct 21 12:30:53 BST 2015
CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1
SERVER IP ADDRESS: 0:0:0:0:0:0:0:1
=


2015-10-21 12:30:53,895 DEBUG [org.jasig.cas.ticket.registry.JpaTicketRegistry] 
- Added ticket 
[TGT-3-KDZzl1jcXb0W6bARCGc0SngtNtdquQ706gblgh34I5W7XzBWrj-localhost:8443] to 
registry.
2015-10-21 12:30:53,909 INFO 
[com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - Audit trail 
record BEGIN
=
WHO: audit:unknown
WHAT: TGT-3-KDZzl1jcXb0W6bARCGc0SngtNtdquQ706gblgh34I5W7XzBWrj-localhost:8443
ACTION: TICKET_GRANTING_TICKET_CREATED
APPLICATION: SSO
WHEN: Wed Oct 21 12:30:53 BST 2015
CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1
SERVER IP ADDRESS: 0:0:0:0:0:0:0:1
=


2015-10-21 12:30:53,931 DEBUG 
[org.jasig.cas.web.support.CookieRetrievingCookieGenerator] - Removed cookie 
with name [CASPRIVACY]
2015-10-21 12:30:53,948 DEBUG 
[org.jasig.cas.web.support.CookieRetrievingCookieGenerator] - Added cookie with 
name [CASTGC] and value 
[TGT-3-KDZzl1jcXb0W6bARCGc0SngtNtdquQ706gblgh34I5W7XzBWrj-localhost:8443]
2015-10-21 12:30:53,964 DEBUG [org.jasig.cas.CentralAuthenticationServiceImpl] 
- Generated service ticket id [ST-3-w3r1jKCesKUtdOfQbzfB-localhost:8443] for 
ticket granting ticket 
[TGT-3-KDZzl1jcXb0W6bARCGc0SngtNtdquQ706gblgh34I5W7XzBWrj-localhost:8443]
2015-10-21 12:30:53,964 DEBUG [org.jasig.cas.ticket.registry.JpaTicketRegistry] 
- Updated ticket 
[TGT-3-KDZzl1jcXb0W6bARCGc0SngtNtdquQ706gblgh34I5W7XzBWrj-localhost:8443].
2015-10-21 12:30:53,965 DEBUG [org.jasig.cas.ticket.registry.JpaTicketRegistry] 
- Added ticket [ST-3-w3r1jKCesKUtdOfQbzfB-localhost:8443] to registry.
2015-10-21 12:30:53,966 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - 
Granted service ticket [ST-3-w3r1jKCesKUtdOfQbzfB-localhost:8443] for service 

Re: [cas-user] Error 500 when validating SAML

2015-10-21 Thread Alberto Cabello Sánchez
> After that, we get an ERROR 500,
> 
> Estado HTTP 500 - java.io.IOException: Server returned HTTP response code: 
> 500 for URL:
> https://localhost:8443/sso/samlValidate?TARGET=https%3A%2F%2Flocalhost%3A8443%2FTestApp11%2Fsso%2FProtectedServlet
> type Informe de Excepción
> mensaje java.io.IOException: Server returned HTTP response code: 500 for URL:
> https://localhost:8443/sso/samlValidate?TARGET=https%3A%2F%2Flocalhost%3A8443%2FTestApp11%2Fsso%2FProtectedServlet
> descripción El servidor encontró un error interno que hizo que no pudiera 
> rellenar este requerimiento.

A 500 error usually writes some messages in Tomcat log file.
Did you look at it?

Also, is all the SSL-related stuff working properly?

-- 
Alberto Cabello Sánchez
Universidad de Extremadura

-- 
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