[cas-user] Re: jboss-eap-7.1.0 stops logging serverstartup logs once it starts deploying cas.war of version 5.3.8

[Abylay]

We've got the same issue. Did someone find a solution?

On Thursday, May 9, 2019 at 6:32:01 PM UTC+6, P Shreyas Holla wrote:
>
> I have deployed CAS 5.3.8 WAR file in JBOSS EAP 7.1.0. But on 
> serverstartup once the JBOSS starts deployment of CAS WAR it stops logging 
> the startup information, Below is the startup log,
>
> 14:19:30,699 INFO  [org.jboss.modules] (main) JBoss Modules version 
> 1.6.0.Final-redhat-1
> 14:19:31,108 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
> 14:19:31,258 INFO  [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss 
> EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
> 14:19:32,466 INFO  [org.jboss.as.controller.management-deprecated] 
> (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the 
> resource at address 
> '/core-service=management/management-interface=http-interface' is deprecated, 
> and may be removed in future version. See the attribute description in the 
> output of the read-resource-description operation to learn more about the 
> deprecation.
> 14:19:32,481 INFO  [org.wildfly.security] (ServerService Thread Pool -- 22) 
> ELY1: WildFly Elytron version 1.1.7.Final-redhat-1
> 14:19:32,483 INFO  [org.jboss.as.controller.management-deprecated] 
> (ServerService Thread Pool -- 27) WFLYCTL0028: Attribute 'security-realm' in 
> the resource at address 
> '/subsystem=undertow/server=default-server/https-listener=https' is 
> deprecated, and may be removed in future version. See the attribute 
> description in the output of the read-resource-description operation to learn 
> more about the deprecation.
> 14:19:33,491 INFO  [org.jboss.as.server] (Controller Boot Thread) 
> WFLYSRV0039: Creating http management service using socket-binding 
> (management-http)
> 14:19:33,505 INFO  [org.xnio] (MSC service thread 1-3) XNIO version 
> 3.5.4.Final-redhat-1
> 14:19:33,511 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO 
> Implementation Version 3.5.4.Final-redhat-1
> 14:19:33,542 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 
> 41) WFLYIO001: Worker 'default' has auto-configured to 24 core threads with 
> 192 task threads based on your 12 available processors
> 14:19:33,547 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 58) 
> WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is 
> set to the default value. This is a danger for environments running multiple 
> servers. Please make sure the attribute value is unique.
> 14:19:33,548 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 50) 
> WFLYNAM0001: Activating Naming Subsystem
> 14:19:33,558 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 43) 
> WFLYRS0016: RESTEasy version 3.0.24.Final-redhat-1
> 14:19:33,560 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread 
> Pool -- 42) WFLYCLINF0001: Activating Infinispan subsystem.
> 14:19:33,564 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 
> 60) WFLYWS0002: Activating WebServices Extension
> 14:19:33,569 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 57) 
> WFLYSEC0002: Activating Security Subsystem
> 14:19:33,571 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) 
> WFLYJSF0007: Activated the following JSF Implementations: [main]
> 14:19:33,575 INFO  [org.jboss.as.connector] (MSC service thread 1-6) 
> WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final-redhat-1)
> 14:19:33,591 INFO  [org.jboss.as.security] (MSC service thread 1-6) 
> WFLYSEC0001: Current PicketBox version=5.0.2.Final-redhat-1
> 14:19:33,602 INFO  [org.jboss.as.connector.subsystems.datasources] 
> (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant 
> driver class org.h2.Driver (version 1.4)
> 14:19:33,604 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) 
> WFLYUT0003: Undertow 1.4.18.Final-redhat-2 starting
> 14:19:33,621 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service 
> thread 1-8) WFLYJCA0018: Started Driver service with driver-name = h2
> 14:19:33,630 INFO  [org.jboss.as.naming] (MSC service thread 1-6) 
> WFLYNAM0003: Starting Naming Service
> 14:19:33,632 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) 
> WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
> 14:19:33,684 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss 
> Remoting version 5.0.5.Final-redhat-1
> 14:19:33,779 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0481: 
> Strict pool slsb-strict-max-pool is using a max instance size of 192 (per 
> class), which is derived from thread worker pool sizing.
> 14:19:33,779 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: 
> Strict pool mdb-strict-max-pool is using a max instance size of 48 (per 
> class), which is derived from the number of CPUs on this host.
> 14:19:33,797 INFO  [org.wildfly.extension.undertow] (ServerService Thread 
> Pool -- 59) WFLYUT0014: Creating file handler for path 
> 

[cas-user] Re: After a month, no tickets created in 4.2.2?

[Abylay]

Hi.
I'm getting the same exception on CAS 5.2.0.
Does anyone know the solution?

On Wednesday, July 20, 2016 at 4:09:59 AM UTC+6, Jeffrey Wong wrote:
>
> After about a month of working perfectly on 4.2.2 deployed to tomcat7, 
> running under java8, randomly the in-memory ticketing system would not 
> create any more tickets. Restarting the tomcat instance fixed it, but I'm 
> wondering why CAS would randomly break on me after working so well! Using a 
> LDAP (AD) backed user base with a mysql backed attribute DB. We have pretty 
> minimal traffic, so I'm not sure why I am seeing issues after such a small 
> amount of time.
>
> Despite having an , no errors have been thrown at 
> the time of issue.
>
> Unfortunately, I've only had the org.springframework.jdbc logger set to 
> debug, and all others at info, so I have very minimal logging around the 
> issue.
>
> I'm noticing both the ldap auth AND the jdbc handlers returning without 
> issues (no errors). ...But no tickets?
>
> Here's a sample of the logs:
>
> 2016-07-19 16:28:16,399 INFO 
> [org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - 
>  
> 2016-07-19 16:28:16,400 DEBUG [org.springframework.jdbc.core.JdbcTemplate] - 
>  
> 2016-07-19 16:28:16,400 DEBUG [org.springframework.jdbc.core.JdbcTemplate] - 
>  ID,username,FirstName,LastName,Email FROM User WHERE UserName = ?]> 
> 2016-07-19 16:28:16,400 DEBUG 
> [org.springframework.jdbc.datasource.DataSourceUtils] -  Connection from DataSource> 
> 2016-07-19 16:28:16,401 DEBUG 
> [org.springframework.jdbc.datasource.DataSourceUtils] -  Connection to DataSource> 
> 2016-07-19 16:28:19,015 INFO 
> [org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - 
>  
> 2016-07-19 16:28:19,015 DEBUG [org.springframework.jdbc.core.JdbcTemplate] - 
>  
> 2016-07-19 16:28:19,015 DEBUG [org.springframework.jdbc.core.JdbcTemplate] - 
>  ID,username,FirstName,LastName,Email FROM User WHERE UserName = ?]> 
> 2016-07-19 16:28:19,015 DEBUG 
> [org.springframework.jdbc.datasource.DataSourceUtils] -  Connection from DataSource> 
> 2016-07-19 16:28:19,017 DEBUG 
> [org.springframework.jdbc.datasource.DataSourceUtils] -  Connection to DataSource> 
>
> Immediately before this, I've seen tickets that are created (an audit log 
> is posted that a ticket granting ticket has been created and validated, and 
> all is good). There are no exceptions thrown between when the tickets were 
> able to be created and when there was this bottleneck.
>
> On the front end, after the logs say 'success' without a ticket created, 
> they are redirected to the main cas login page. Reproducing this is also 
> difficult as it will stop intermittently, without warning.
>
> What are the best ways to debug or resolve these sorts of issues? What 
> could be causing this issue?
>
> Thanks in advance,
> Jeff
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/355de671-ae64-4b26-863b-b933a056a649%40apereo.org.

[cas-user] Incorrect RequiredHandlers

[Abylay]

Hello, we are using CAS 5.2.0

We need to filter some Auth handlers by service definitions.
As it says 
here 
https://apereo.github.io/cas/5.2.x/installation/Configuring-Service-Required-AuthN.html
 
we are using requiredHandlers property.
But when RegisteredServiceAuthenticationHandlerResolver resolves handlers 
for an OIDC service, it gets required handlers from RegexRegisteredService 
definition, not from actual OIDC service definition.


Is it ok to try to "fix" it in 
RegisteredServiceAuthenticationHandlerResolver? 
Does anyone have any suggestions? 

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/d9cfdf9e-e176-4841-a1a3-91b73382921a%40apereo.org.

Re: [cas-user] Re: CAS + Oauth2.0 + Redirect

[Abylay]

We are using 5.2.0 and we applied mentioned above changes to 
TerminateSessionAction.java 
<https://github.com/apereo/cas/blob/master/support/cas-server-support-actions/src/main/java/org/apereo/cas/web/flow/logout/TerminateSessionAction.java>
.
But it doesn't help in a situation when user stays to long on CAS login 
page and web session gets timed out. In that case pac4JRequestedUrl gets 
lost with the session and user after login will be redirected to /.
So we ended up changing both DefaultSecurityLogic and DefaultCallbackLogic 
to save pac4JRequestedUrl in cookies besides saving it to session.  

On Tuesday, January 29, 2019 at 6:42:44 PM UTC+6, Geoff wrote:
>
> I ran into this in 5.1.x and fixed it by modifying 
> TerminateSessionAction.java to preserve the pac4JRequestedUrl when killing 
> the session.
>
> I found this fix in a newer version of TerminateSessionAction, I thought 
> it was made prior to 5.2.5 but maybe not.
>
>
> https://github.com/apereo/cas/blob/master/support/cas-server-support-actions/src/main/java/org/apereo/cas/web/flow/logout/TerminateSessionAction.java
>
>
>
> On Jan 28, 2019, at 9:45 PM, Abylay > 
> wrote:
>
> Hi, does anyone have solution for this?
>
> On Monday, July 2, 2018 at 5:38:25 PM UTC+6, Diego Henrique Pagani wrote:
>>
>> Hi everyone,
>>
>>
>> i'm having an issue. I have some application that delegates 
>> authentication to CAS 5.2.5 using OAuth2.0 protocol. When someone not 
>> authenticated access the application, the application redirects to CAS. If 
>> the person do not authenticate after some time (or delete the cookies) and 
>> submit the form, CAS authenticate the person but, instead of redirect to 
>> the service mentioned in the URL param, it redirects to "/".
>>
>> After some debbugging, I found out that the class 
>> "DefaultCallbackLogin.java", the method "redirectToOriginallyRequestedUrl" 
>> does the job to redirect, but, it get's from the Session, not from the URL, 
>> so, erasing the cookies or have them invalid, lost the redirect.
>>
>> Does someone know how to solve that issue? Because some users are getting 
>> lost, causing an increase number of ticket relating this issue.
>>
>> Thank you 
>>
>>
>> -- 
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> - Contributions: https://goo.gl/mh7qDG
> --- 
> 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 cas-user+u...@apereo.org .
> To view this discussion on the web visit 
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/317a9de0-e82d-4829-9912-087bfd16efd8%40apereo.org
>  
> <https://groups.google.com/a/apereo.org/d/msgid/cas-user/317a9de0-e82d-4829-9912-087bfd16efd8%40apereo.org?utm_medium=email_source=footer>
> .
>
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/51c807f1-334d-4e7e-8126-5f62b4f2cfe8%40apereo.org.

[cas-user] Custom Webflow

[Abylay]

I found how one can extend existing Login and Logout webflows here 

.

But is it possible to add new web flow to CAS 5.2.X ?

If so how can it be done?

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/4c0b5248-3186-48ac-9d51-0be3cd6932ed%40apereo.org.

[cas-user] Re: Extends LdapAuthenticationHandler in cas 5.2

[Abylay]

>
> Did you try to add the dependency with NotFound class?
>

1. Find the class in your IDE.
2. Add the dependency in which this class is located.

For AbstractUsernamePasswordAuthenticationHandler it would be 


org.apereo.cas
cas-server-core-authentication
${cas.version}
compile




-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/3f98b364-ca3c-429f-a8c8-d074e7046e0c%40apereo.org.

[cas-user] Spnego ERROR on CAS 5.2.0

[Abylay]

Hello!
I'm trying to configure Spnego on CAS 5.2.0 

I added required dependency to pom file:


org.apereo.cas
cas-server-support-spnego-webflow
${cas.version}



I have an SPN account and working keytab file. I've configured krb5.conf 
and login.conf as it says in here SPNEGO-Authentication.html 

I configured my browsers to support Kerberos.
Here is the SPNEGO part of cas configuration file:
# SPNEGO
# cas.authn.spnego.kerberosConf=
cas.authn.spnego.mixedModeAuthentication=true
# cas.authn.spnego.cachePolicy=600
# cas.authn.spnego.timeout=30
cas.authn.spnego.jcifsServicePrincipal=HTTP/kerberos.mycompany...@mycompany.kz
# cas.authn.spnego.jcifsNetbiosWins=
cas.authn.spnego.loginConf=file:D:\\etc\\cas\\config\\login.conf
# cas.authn.spnego.ntlmAllowed=true
# cas.authn.spnego.hostNamePatternString=.+
# cas.authn.spnego.jcifsUsername=
# cas.authn.spnego.useSubjectCredsOnly=false
# cas.authn.spnego.supportedBrowsers=MSIE,Trident,Firefox,AppleWebKit
# cas.authn.spnego.jcifsDomainController=
# cas.authn.spnego.dnsTimeout=2000
# cas.authn.spnego.hostNameClientActionStrategy=hostnameSpnegoClientAction
cas.authn.spnego.kerberosKdc=dc01.mycompany.kz
# cas.authn.spnego.alternativeRemoteHostAttribute=alternateRemoteHeader
# cas.authn.spnego.jcifsDomain=
# cas.authn.spnego.ipsToCheckPattern=127.+
# cas.authn.spnego.kerberosDebug=true
# cas.authn.spnego.send401OnAuthenticationFailure=true
cas.authn.spnego.kerberosRealm=MYCOMPANY.KZ
# cas.authn.spnego.ntlm=false
# cas.authn.spnego.principalWithDomainName=false
cas.authn.spnego.jcifsServicePassword=1q2w3e4r

When I open login page there is the next error on CAS logs:

2018-01-09 13:47:33,472 INFO 
[org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - 
2018-01-09 13:47:33,487 DEBUG 
[org.apereo.cas.support.oauth.validator.OAuth20AuthenticationServiceSelectionStrategy]
 
- 
2018-01-09 13:47:33,488 DEBUG 
[org.apereo.cas.authentication.adaptive.DefaultAdaptiveAuthenticationPolicy] 
- 
2018-01-09 13:47:33,490 DEBUG 
[org.apereo.cas.authentication.adaptive.DefaultAdaptiveAuthenticationPolicy] 
- 
2018-01-09 13:47:33,490 DEBUG 
[org.apereo.cas.authentication.adaptive.DefaultAdaptiveAuthenticationPolicy] 
- 
2018-01-09 13:47:33,491 DEBUG [org.apereo.cas.web.support.WebUtils] - 

2018-01-09 13:47:33,491 DEBUG [org.apereo.cas.web.support.WebUtils] - 

2018-01-09 13:47:33,493 DEBUG 
[org.apereo.cas.authentication.RegisteredServiceAuthenticationHandlerResolver] 
- 
2018-01-09 13:47:33,494 DEBUG 
[org.apereo.cas.support.spnego.authentication.handler.support.JcifsSpnegoAuthenticationHandler]
 
- 
2018-01-09 13:47:33,526 DEBUG 
[org.apereo.cas.support.spnego.authentication.handler.support.JcifsSpnegoAuthenticationHandler]
 
- 
2018-01-09 13:47:33,527 DEBUG 
[org.apereo.cas.support.spnego.authentication.handler.support.JcifsSpnegoAuthenticationHandler]
 
- 
2018-01-09 13:47:33,528 DEBUG 
[org.apereo.cas.support.spnego.authentication.handler.support.JcifsSpnegoAuthenticationHandler]
 
- 
2018-01-09 13:47:33,530 DEBUG 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 
<[JcifsSpnegoAuthenticationHandler] exception details: [Principal is null, 
the processing of the SPNEGO Token failed].>
2018-01-09 13:47:33,531 DEBUG 
[org.apereo.cas.authentication.handler.support.AbstractUsernamePasswordAuthenticationHandler]
 
- 
2018-01-09 13:47:33,532 DEBUG 
[org.apereo.cas.authentication.handler.support.AbstractUsernamePasswordAuthenticationHandler]
 
- 
2018-01-09 13:47:33,532 DEBUG 
[org.apereo.cas.authentication.handler.support.AbstractUsernamePasswordAuthenticationHandler]
 
- 
2018-01-09 13:47:33,533 ERROR 
[org.apereo.cas.authentication.PolicyBasedAuthenticationManager] - 

2018-01-09 13:47:33,534 INFO 
[org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - 

Has anyone here had the same issue or knows how to solve it?
I suspect it's a bug.

Thanks.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/7cfd9400-7e6f-4be4-b125-b609cdba15d6%40apereo.org.

[cas-user] Re: CAS 5.2. Custom login page. Add more required item login

[Abylay]

Though first you need to add new field in "loginform.html".

On Tuesday, December 26, 2017 at 6:04:58 PM UTC+6, Abylay wrote:
>
> You can redefine file login-webflow.xml and bind new property 
> to credential. Just like properties "username", "password" are done already.
> Then new property will be available from "credential" to use whenever you 
> choose to.
>
> On Monday, December 25, 2017 at 1:04:51 PM UTC+6, J0ny Trinh wrote:
>>
>> Dear all
>>
>> I want to create SSO with CAS 5.2 with authentication with JDBC.
>> With only username and password have no problem.
>>
>> But i want to add 1 item to login(example: department id). I have no Idea 
>> for that.
>> Any one could help me.
>>
>> Thanks
>>
>>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/4f5bdf0c-5b0b-48a3-88b0-8fee05fe1cae%40apereo.org.

[cas-user] Re: CAS 5.2. Custom login page. Add more required item login

[Abylay]

You can redefine file login-webflow.xml and bind new property 
to credential. Just like properties "username", "password" are done already.
Then new property will be available from "credential" to use whenever you 
choose to.

On Monday, December 25, 2017 at 1:04:51 PM UTC+6, J0ny Trinh wrote:
>
> Dear all
>
> I want to create SSO with CAS 5.2 with authentication with JDBC.
> With only username and password have no problem.
>
> But i want to add 1 item to login(example: department id). I have no Idea 
> for that.
> Any one could help me.
>
> Thanks
>
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
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 cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/b51d22b2-e18d-4579-bac0-2a9876361cf9%40apereo.org.

[cas-user] Re: CAS 5.1.4 Server with JDBC and SAML - Deployment error on Wildfly 10

[Abylay]

On Tuesday, September 26, 2017 at 2:26:02 AM UTC+6, SebastianU wrote:
>
> Hi,
>
> I'm migrating to Wildfly 10 and CAS 5.x and I'm getting errors deploying 
> default overlay template...
>
> My pom.xml includes:
>
>
> 
> org.apereo.cas
> cas-server-support-jdbc
> ${cas.version}
> 
> 
> org.apereo.cas
> cas-server-support-saml
> ${cas.version}
> 
>
> ...
> 5.1.4
>
> Deployment fails with following error:
>
> 22:16:43,264 WARN 
>  
> [org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext]
>  
> (ServerService Thread Pool -- 112) Exception encountered during context 
> initialization - cancelling refresh attempt: 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'shibboleth.OpenSAMLConfig' defined in class path resource 
> [org/apereo/cas/config/CoreSamlConfiguration.class]: Bean instantiation via 
> factory method failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [org.apereo.cas.support.saml.OpenSamlConfigBean]: Factory method 
> 'openSamlConfigBean' threw exception; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'shibboleth.ParserPool' defined in class path resource 
> [org/apereo/cas/config/CoreSamlConfiguration.class]: Bean instantiation via 
> factory method failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [net.shibboleth.utilities.java.support.xml.BasicParserPool]: Factory method 
> 'parserPool' threw exception; nested exception is 
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> com.sun.org.apache.xerces.internal.util.SecurityManager from [Module 
> "deployment.cas.war:main" from Service Module Loader]
> 22:16:43,279 ERROR [org.springframework.boot.SpringApplication] 
> (ServerService Thread Pool -- 112) Application startup failed: 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'shibboleth.OpenSAMLConfig' defined in class path resource 
> [org/apereo/cas/config/CoreSamlConfiguration.class]: Bean instantiation via 
> factory method failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [org.apereo.cas.support.saml.OpenSamlConfigBean]: Factory method 
> 'openSamlConfigBean' threw exception; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'shibboleth.ParserPool' defined in class path resource 
> [org/apereo/cas/config/CoreSamlConfiguration.class]: Bean instantiation via 
> factory method failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [net.shibboleth.utilities.java.support.xml.BasicParserPool]: Factory method 
> 'parserPool' threw exception; nested exception is 
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> com.sun.org.apache.xerces.internal.util.SecurityManager from [Module 
> "deployment.cas.war:main" from Service Module Loader]
> at 
> org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:599)
> ...
> Caused by: org.springframework.beans.BeanInstantiationException: Failed to 
> instantiate [org.apereo.cas.support.saml.OpenSamlConfigBean]: Factory 
> method 'openSamlConfigBean' threw exception; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'shibboleth.ParserPool' defined in class path resource 
> [org/apereo/cas/config/CoreSamlConfiguration.class]: Bean instantiation via 
> factory method failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [net.shibboleth.utilities.java.support.xml.BasicParserPool]: Factory method 
> 'parserPool' threw exception; nested exception is 
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
> com.sun.org.apache.xerces.internal.util.SecurityManager from [Module 
> "deployment.cas.war:main" from Service Module Loader]
> at 
> org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:189)
> at 
> org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:588)
> ... 37 more
> Caused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 'shibboleth.ParserPool' defined in class path 
> resource [org/apereo/cas/config/CoreSamlConfiguration.class]: Bean 
> instantiation via factory method failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [net.shibboleth.utilities.java.support.xml.BasicParserPool]: Factory method 
> 'parserPool' threw exception; nested exception is 
> java.lang.RuntimeException: java.lang.ClassNotFoundException: 
>