First of all, thanks a lot for your help and support, they were like life
savers.
Secondly, I'm afraid this is not the correct place to ask for issues and
support, so is it? if not please route me there?
Now, I've configured the `cas-management-webapp`, from the link you
previously sent, to use my CAS server with JSON service registry. The
settings are the default ones for the services definition directory and the
user is the default "casuser" one.
The good thing is I could deploy it correctly but when trying to use it the
following error appears in the management web page:
> The CAS management webapp is Unavailable
> There was an error trying to complete your request. Please notify your
> support desk or try again.
Attached file contains the `catalina.out` needed log.
On Thu, Apr 16, 2015 at 12:26 PM, Misagh Moayyed <[email protected]>
wrote:
> No you’re not. We just have not kept the 4.1 branch up to date because
> it’s still in dev and subject to change.
>
>
>
> Seems like you’re just missing a few settings. Compare your
> cas.properties with this:
>
>
> https://github.com/Jasig/cas/blob/master/cas-server-webapp/src/main/webapp/WEB-INF/cas.properties
>
>
>
> and add the missing settings.
>
>
>
> *From:* Nouman Fallouh [mailto:[email protected]]
> *Sent:* Thursday, April 16, 2015 2:18 AM
>
> *To:* [email protected]
> *Subject:* Re: [cas-user] JSON Service Management
>
>
>
> I'm trying to redo things with version *4.1.0-SNAPSHOT* so I cloned the
> CAS overlay template from here:
>
> https://github.com/UniconLabs/simple-cas4-overlay-template/tree/4.1
>
> and switched to the* branch 4.1*, moved the properties files to `
> */etc/cas41*` and modified the `*propertyFileConfigurer.xml*` to point to
> the correct file:
>
> <util:properties id="casProperties"
> location="file:/etc/cas41/cas.properties" />
> <context:property-placeholder properties-ref="casProperties" />
>
>
>
> Then mvn clean package works fine but when deploying it failed with the
> following exception in the `catalina.out` log file:
>
> ERROR [org.springframework.web.context.ContextLoader] - <Context
> initialization failed
> org.springframework.beans.factory.BeanDefinitionStoreException: Invalid
> bean definition with name 'cookieCipherExecutor' defined in ServletContext
> resource [/WEB-INF/sp
> ring-configuration/ticketGrantingTicketCookieGenerator.xml]: Could not
> resolve placeholder 'tgc.encryption.key' in string value
> "${tgc.encryption.key}"; nested exceptio
> n is java.lang.IllegalArgumentException: Could not resolve placeholder
> 'tgc.encryption.key' in string value "${tgc.encryption.key}"
>
> ....
>
> ...
>
> Caused by: java.lang.IllegalArgumentException: Could not resolve
> placeholder 'tgc.encryption.key' in string value "${tgc.encryption.key}"
>
>
>
> Am I missing something here? cause this is default installation ??!!
>
>
>
> Best regards
>
>
>
>
>
> On Mon, Apr 13, 2015 at 12:56 PM, Misagh Moayyed <[email protected]>
> wrote:
>
> 4.1.0-SNAPSHOT should work, yes. I can’t exactly comment on the next
> release date, but I can tell you we are close. The only major issue pending
> is the redesigning of the management webapp and I have been working on that
> issue for a while with a UX expert to make it more adopter friendly and
> functional. Once that is taken care of, we should be able to proceed
> forward.
>
>
>
> *From:* Nouman Fallouh [mailto:[email protected]]
> *Sent:* Monday, April 13, 2015 2:47 AM
> *To:* [email protected]
> *Subject:* Re: [cas-user] JSON Service Management
>
>
>
> Yes indeed, I discovered my fault when seeing that the `
> *JsonServiceRegistryDao*` defined in the *v4.1.0-SNAPSHOT *but not in the
> one I'm using *v4.0.1.*
>
>
>
> Do you think that if I used the new version *v4.1.0-SNAPSHOT *in my
> pom.xml file might solve my problem?
>
>
>
> Honestly, I would rather not using alternative solutions, when do you
> think the new release might be available? if it's not that long, I could
> use the `*InMemoryServiceRegistryDaoImpl*` instead during this period.
>
>
>
> Best regards
>
>
>
>
>
>
>
> On Mon, Apr 13, 2015 at 12:02 PM, Misagh Moayyed <[email protected]>
> wrote:
>
> This is because you are trying to use functionality that does not exist in
> CAS4. The docs you reference below are in “development” (as the note at the
> top of the page says) and apply to code that not released yet.
>
>
>
> This is the correct link for CAS 4.0:
>
> http://jasig.github.io/cas/4.0.x/installation/Service-Management.html
>
>
>
> This might be a viable option for CAS4 if you are looking for alternative
> service registry options:
>
> https://github.com/unicon-cas-addons/cas-addon-yaml-services-registry
>
>
>
> *From:* Nouman Fallouh [mailto:[email protected]]
> *Sent:* Sunday, April 12, 2015 11:22 PM
> *To:* [email protected]
> *Subject:* [cas-user] JSON Service Management
>
>
>
> Hi,
>
>
>
> I'd finished setting up the CAS server v4 and now trying to deploy service
> management application.
>
> Therefor I've got the `*cas-management-webapp*` which by default is
> shipped with `*JsonServiceRegistryDao*` where my CAS server is shipped
> with `*InMemoryServiceRegistryDaoImpl*`.
>
> I want to use the JSON one and I read here:
>
>
> http://jasig.github.io/cas/development/installation/Service-Management.html#services-registry
>
> that this settings should be unified in both applications, so when using
> the JSON in the CAS server I got this error when deploying the application
> in tomcat v8:
>
>
>
> 2015-04-12 22:45:40,498 ERROR
> [org.springframework.web.context.ContextLoader] - <Context initialization
> failed>
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'ticketRegistryCleaner' defined in ServletContext resource
> [/WEB-INF/spring-confi
> guration/ticketRegistry.xml]: Cannot resolve reference to bean
> 'logoutManager' while setting bean property 'logoutManager'; nested
> exception is org.springframework.bean
> s.factory.BeanCreationException: Error creating bean with name
> 'logoutManager' defined in ServletContext resource
> [/WEB-INF/spring-configuration/applicationContext.xml]
> : Cannot resolve reference to bean 'servicesManager' while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Er
> ror creating bean with name 'servicesManager' defined in ServletContext
> resource [/WEB-INF/spring-configuration/applicationContext.xml]: Cannot
> resolve reference to bea
> n 'serviceRegistryDao' while setting constructor argument; nested
> exception is
> org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find
> class [org.ja
> sig.cas.services.JsonServiceRegistryDao] for bean with name
> 'serviceRegistryDao' defined in ServletContext resource
> [/WEB-INF/deployerConfigContext.xml]; nested excepti
> on is java.lang.ClassNotFoundException:
> org.jasig.cas.services.JsonServiceRegistryDao
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:326)
>
>
>
> It looks like it can't see the
> `org.jasig.cas.services.JsonServiceRegistryDao` how does this come?
>
>
>
> I'm really stuck there, any help is appreciated.
>
>
>
>
>
> --
>
> You are currently subscribed to [email protected] as:
> [email protected]
>
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
> --
>
> You are currently subscribed to [email protected] as:
> [email protected]
>
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
>
>
>
>
> --
>
> You are currently subscribed to [email protected] as:
> [email protected]
>
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
> --
>
> You are currently subscribed to [email protected] as:
> [email protected]
>
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
>
>
>
>
> --
>
> You are currently subscribed to [email protected] as:
> [email protected]
>
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
> --
> You are currently subscribed to [email protected] as:
> [email protected]
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
>
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user2015-04-16 13:56:04,262 INFO [com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN
=============================================================
WHO: casuser+password
WHAT: supplied credentials: [casuser+password]
ACTION: AUTHENTICATION_SUCCESS
APPLICATION: CAS
WHEN: Thu Apr 16 13:56:04 EEST 2015
CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1
SERVER IP ADDRESS: 0:0:0:0:0:0:0:1
=============================================================
>
2015-04-16 13:56:04,265 INFO [com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN
=============================================================
WHO: casuser+password
WHAT: TGT-**********************************************GrAfmhfzMc-cas01.example.org
ACTION: TICKET_GRANTING_TICKET_CREATED
APPLICATION: CAS
WHEN: Thu Apr 16 13:56:04 EEST 2015
CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1
SERVER IP ADDRESS: 0:0:0:0:0:0:0:1
=============================================================
>
2015-04-16 13:56:04,360 INFO [org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - <AcceptUsersAuthenticationHandler successfully authenticated casuser+password>
2015-04-16 13:56:04,361 INFO [org.jasig.cas.authentication.PolicyBasedAuthenticationManager] - <Authenticated casuser with credentials [casuser+password].>
2015-04-16 13:56:04,361 INFO [com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN
=============================================================
WHO: casuser+password
WHAT: supplied credentials: [casuser+password]
ACTION: AUTHENTICATION_SUCCESS
APPLICATION: CAS
WHEN: Thu Apr 16 13:56:04 EEST 2015
CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1
SERVER IP ADDRESS: 0:0:0:0:0:0:0:1
=============================================================
>
2015-04-16 13:56:04,367 INFO [org.jasig.cas.CentralAuthenticationServiceImpl] - <Granted ticket [ST-1-XIuKcqVC1Lut1lfzEc7H-cas01.example.org] for service [https://localhost:8443/cas-management/j_spring_cas_security_check] for user [casuser]>
2015-04-16 13:56:04,368 INFO [com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN
=============================================================
WHO: casuser
WHAT: ST-1-XIuKcqVC1Lut1lfzEc7H-cas01.example.org for https://localhost:8443/cas-management/j_spring_cas_security_check
ACTION: SERVICE_TICKET_CREATED
APPLICATION: CAS
WHEN: Thu Apr 16 13:56:04 EEST 2015
CLIENT IP ADDRESS: 0:0:0:0:0:0:0:1
SERVER IP ADDRESS: 0:0:0:0:0:0:0:1
=============================================================
>
2015-04-16 13:56:05,571 INFO [com.github.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN
=============================================================
WHO: audit:unknown
WHAT: ST-1-XIuKcqVC1Lut1lfzEc7H-cas01.example.org
ACTION: SERVICE_TICKET_VALIDATED
APPLICATION: CAS
WHEN: Thu Apr 16 13:56:05 EEST 2015
CLIENT IP ADDRESS: 127.0.0.1
SERVER IP ADDRESS: 127.0.0.1
=============================================================
>
2015-04-16 13:56:23,922 INFO [org.jasig.cas.services.DefaultServicesManagerImpl] - <Reloading registered services.>
2015-04-16 13:56:23,922 INFO [org.jasig.cas.services.DefaultServicesManagerImpl] - <Loaded 2 services.>
