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

2019-05-09 Thread P Shreyas Holla
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 INF

[cas-user] How to build CAS 5.3.8 without spring boot dependecies.

2019-03-17 Thread P Shreyas Holla
Hi, I used CAS overlay to build CAS 5.3.8 WAR. But once I deployed the WAR on WildFly 10.0.0.Final, it stops Wildfly console logging to stop as shown below, WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war") WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-nam

[cas-user] Re: CAS 5.3.8 deployment on Wildfly 5.3.8 is succesfull but it makes the wildfly console logging to stop

2019-03-13 Thread P Shreyas Holla
Correction : WIldFly version 10.0.0 FInal On Thursday, March 14, 2019 at 10:44:38 AM UTC+5:30, P Shreyas Holla wrote: > > Hi, > > CAS 5.3.8 deployment on Wildfly 5.3.8 is succesfull but it makes the > wildfly console logging to stop with following logs, > > WFLYJCA0001: Bo

[cas-user] CAS 5.3.8 deployment on Wildfly 5.3.8 is succesfull but it makes the wildfly console logging to stop

2019-03-13 Thread P Shreyas Holla
Hi, CAS 5.3.8 deployment on Wildfly 5.3.8 is succesfull but it makes the wildfly console logging to stop with following logs, WFLYJCA0001: Bound data source [java:/jdbc/WSREGISTRY] IJ020018: Enabling for java:/DB2DSXA WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] WFLYJCA0001

Re: [cas-user] CAS 5.3.8 deployment on Wildfly 10.0.0 Final fails

2019-02-25 Thread P Shreyas Holla
Hi, We are referring to JDK 1.8_191. On Monday, February 25, 2019 at 3:08:00 PM UTC+5:30, casuser wrote: > > Which Java version are you referring to? > > On Mon, Feb 25, 2019 at 5:30 PM P Shreyas Holla > wrote: > >> Hi, >> >> We are deploying CAS 5.3.8 WAR on

[cas-user] CAS 5.3.8 deployment on Wildfly 10.0.0 Final fails

2019-02-25 Thread P Shreyas Holla
Hi, We are deploying CAS 5.3.8 WAR on Wildfly 10.0.0 Final, the deployment fails with following log, 14:57:45,639 WARN [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0013: Deployment deployment "cas-server-webapp-5.3.8.war" contains CDI annotations but no bean archive was not foun

Re: [cas-user] Re: CAS integration with multiple OpenID Providers

2019-02-13 Thread P Shreyas Holla
e accessToken. Thanks Shreyas On Wednesday, February 13, 2019 at 3:43:25 PM UTC+5:30, P Shreyas Holla wrote: > > Jérôme, is it possible to mention the application url as part of > /clientredirect like " > http://localhost:8080/cas/clientredirect?client_name=Google2Client&redirect

Re: [cas-user] Re: CAS integration with multiple OpenID Providers

2019-02-13 Thread P Shreyas Holla
; Jérôme > > > Le mer. 23 janv. 2019 à 05:54, P Shreyas Holla > a écrit : > >> >> leleuj , we want to achieve something like* http://localhost:8080/cas >> <http://localhost:8080/cas>?client_name=AzureAdClient* for Azure and >> *http://localhost:8080/ca

[cas-user] how to handle Logout scenario with CAS-Openid

2019-02-12 Thread P Shreyas Holla
HI, Can anyone let me know how to handle logout scenario in-case of openid with CAS. Thanks & Regards Shreyas -- - 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 rece

Re: [cas-user] Re: CAS integration with multiple OpenID Providers

2019-02-12 Thread P Shreyas Holla
Thanks Jerome, it worked with 5.3.7. On Wednesday, January 23, 2019 at 9:18:40 PM UTC+5:30, P Shreyas Holla wrote: > > Thanks Jerome, will test the same and will update. > > On Wednesday, January 23, 2019 at 1:29:10 PM UTC+5:30, leleuj wrote: >> >> Hi, >> >>

Re: [cas-user] Re: CAS integration with multiple OpenID Providers

2019-01-23 Thread P Shreyas Holla
est regards, > Jérôme > > > Le mer. 23 janv. 2019 à 05:54, P Shreyas Holla > a écrit : > >> >> leleuj , we want to achieve something like* http://localhost:8080/cas >> <http://localhost:8080/cas>?client_name=AzureAdClient* for Azure and >> *

[cas-user] Re: CAS integration with multiple OpenID Providers

2019-01-22 Thread P Shreyas Holla
hanks. > Best regards, > Jéôme > > > Le mardi 22 janvier 2019 09:58:39 UTC+1, P Shreyas Holla a écrit : >> >> Suppose we have User1 and User2. >> >> 1)Whenever user1 acesses the application URL, he has to be redirected to >> google login page, >

[cas-user] Re: CAS integration with multiple OpenID Providers

2019-01-22 Thread P Shreyas Holla
Suppose we have User1 and User2. 1)Whenever user1 acesses the application URL, he has to be redirected to google login page, 2) Whenever user2 acesses the application URL, he has to be redirected to microsoft Azure login page. On Tuesday, January 22, 2019 at 2:20:25 PM UTC+5:30, P Shreyas

[cas-user] CAS integration with multiple OpenID Providers

2019-01-22 Thread P Shreyas Holla
We need to integrate CAS with multiple OpenID Providers like with Google and Azure. How can we achieve it? -- - 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