Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Ray Bon]

Va,

'usage' in mvnrepository means how many projects have a dependency on that 
project, not number of downloads.

Ray

On Sun, 2019-05-19 at 07:28 -0700, Va Sja wrote:
Hmm...
..looks really like "Security through obscurity" :((
Guys - how many peoples use CAS worldwide?
looks like nobody?

SRC: https://mvnrepository.com/artifact/org.apereo.cas/cas-server-webapp



Am Freitag, 31. August 2018 13:05:02 UTC+2 schrieb 党田力:
I had test on 5.2.6 adn 5.2.7 version
Only append `cas-server-support-json-service-registry` to pom.xml, the 
'cas.serviceRegistry.initFromJson=true' is worked.
Only append `cas-server-support-jpa-service-registry` to pom.xml, the database 
is worked.
But I append both them, the services defined in json is not loaded.

On 5.1.9 version works.


在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：
Lionel and Jann,

Did you ever have the JSON service registry working? If not, I recommend that 
you take all the JPA stuff out of pom.xml and cas.properties and get that 
working correctly first, so that you're only trying to debug one thing at a 
time. Once you have the JSON service registry working correctly, for both the 
main server and the management webapp, then it's time to move things to JPA.

The basic steps for moving to JPA *should* be this:

1. REMOVE the "cas-server-support-json-service-registry" dependency from 
pom.xml (server and management webapp)

2. Add the "cas-server-support-jpa-service-registry" dependency and whatever 
other dependencies go with it to pom.xml (server and management webapp)

3. Rebuild the server and management webapp

4. In the server's cas.properties file, include BOTH of these lines:

cas.serviceRegistry.json.location: file:/etc/cas/services
cas.serviceRegistry.initFromJson:  true

The first line should already be there (since before you start these steps 
you're using the JSON service registry), but you must add the second line.

5. Add all the lines you need to configure the JPA service registry to the 
server's cas.properties file.

6. Start the CAS server (do not start the management webapp). You should see it 
load the services from the JSON files (again, this should already be working 
before you start) and then it will magically save them into the JPA registry.

7. Shut the server down.

8. Check the database to see that the services actually got loaded there. If 
not, this is where you need to start debugging. And the first step of that 
would be setting the log level to "debug" in log4j2.xml, and adding whatever 
Logger configuration you need to make the Oracle JDBC library log for you as 
well.

Once you've got the services loaded into the database

9. Remove the "cas.serviceRegistry.json.location" and 
"cas.serviceRegistry.initFromJson" properties from the server's cas.properties 
file.

10. Remove the "cas.serviceRegistry.json.location" property from, and add all 
the JPA properties to, the management webapp's management.properties file.

At least, that's the procedure I followed to get the MongoDB service registry 
working (see 
https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
 I've not used the JPA stuff at all, so no guarantees, but I don't see why it 
should be any different.

--Dave



--

DAVID A. CURRY, CISSP
DIRECTOR OF INFORMATION SECURITY
INFORMATION TECHNOLOGY

71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300 x4728 • david.cu...@newschool.edu

[The New School]

On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  wrote:
Changing in "cas.properties"  
'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
'cas.serviceRegistry.json.location:foobar:/etc/cas/services'

The above does not generate an error message --- is that a sign it's not loaded?


On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
I'm working with Jann -- attached is our pom file (we call the jar my-cas -- 
which is reflected in the URLs).

It does not look like the JSON file is loaded -- I don't think it's pom related 
--- but at the moment we are both stumped so anything goes.

2018-05-14 20:23:17,715 WARN [org.apereo.cas.services.web.ServiceThemeResolver] 
- http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
 or service access is disallowed. Using default theme [cas-theme-default]>

On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:

Attached is my 'cas.properties' file ---  in case I may be missing something 
there (very likely)


On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
I had a minor Eureka moment --- but it came to fraught (partially).

I has a typo in the 'cas.properties' file: 
cas.serviceRegistry.json.location:file:/etc/cas/service

i,e, 'service' instead of 'services' --- corrected now (validated that the json 
files are in '/etc/cas/services').

But still no-go...any ideas will be matched by the maximum Karma I can 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Va Sja]

Hmm...
..looks really like "Security through obscurity" :((
Guys - how many peoples use CAS worldwide? 
looks like nobody?

SRC: https://mvnrepository.com/artifact/org.apereo.cas/cas-server-webapp



Am Freitag, 31. August 2018 13:05:02 UTC+2 schrieb 党田力:
>
> I had test on 5.2.6 adn 5.2.7 version
> Only append `cas-server-support-json-service-registry` to pom.xml, the '
> cas.serviceRegistry.initFromJson=true' is worked.
> Only append `cas-server-support-jpa-service-registry` to pom.xml, the 
> database is worked.
> But I append both them, the services defined in json is not loaded.
>
> On 5.1.9 version works.
>
>
> 在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：
>>
>> Lionel and Jann,
>>
>> Did you ever have the JSON service registry working? If not, I recommend 
>> that you take all the JPA stuff out of pom.xml and cas.properties and get 
>> that working correctly first, so that you're only trying to debug one thing 
>> at a time. Once you have the JSON service registry working correctly, for 
>> both the main server and the management webapp, then it's time to move 
>> things to JPA.
>>
>> The basic steps for moving to JPA *should* be this:
>>
>> 1. REMOVE the "cas-server-support-json-service-registry" dependency from 
>> pom.xml (server and management webapp)
>>
>> 2. Add the "cas-server-support-jpa-service-registry" dependency and 
>> whatever other dependencies go with it to pom.xml (server and management 
>> webapp)
>>
>> 3. Rebuild the server and management webapp
>>
>> 4. In the server's cas.properties file, include BOTH of these lines:
>>
>> cas.serviceRegistry.json.location: file:/etc/cas/services
>> cas.serviceRegistry.initFromJson:  true
>>
>>
>> The first line should already be there (since before you start these 
>> steps you're using the JSON service registry), but you must add the second 
>> line.
>>
>> 5. Add all the lines you need to configure the JPA service registry to 
>> the server's cas.properties file.
>>
>> 6. Start the CAS server (do not start the management webapp). You should 
>> see it load the services from the JSON files (again, this should already be 
>> working before you start) and then it will magically save them into the JPA 
>> registry.
>>
>> 7. Shut the server down.
>>
>> 8. Check the database to see that the services actually got loaded there. 
>> If not, this is where you need to start debugging. And the first step of 
>> that would be setting the log level to "debug" in log4j2.xml, and adding 
>> whatever Logger configuration you need to make the Oracle JDBC library log 
>> for you as well.
>>
>> Once you've got the services loaded into the database
>>
>> 9. Remove the "cas.serviceRegistry.json.location" and 
>> "cas.serviceRegistry.initFromJson" properties from the server's 
>> cas.properties file.
>>
>> 10. Remove the "cas.serviceRegistry.json.location" property from, and add 
>> all the JPA properties to, the management webapp's management.properties 
>> file.
>>
>> At least, that's the procedure I followed to get the MongoDB service 
>> registry working (see 
>> https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
>>  
>> I've not used the JPA stuff at all, so no guarantees, but I don't see why 
>> it should be any different.
>>
>> --Dave
>>
>>
>> --
>>
>> DAVID A. CURRY, CISSP
>> *DIRECTOR OF INFORMATION SECURITY*
>> INFORMATION TECHNOLOGY
>>
>> 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
>> +1 212 229-5300 x4728 • david.cu...@newschool.edu
>>
>> [image: The New School]
>>
>> On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  
>> wrote:
>>
>>> Changing in "cas.properties"  
>>> 'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
>>> 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'
>>>
>>> The above does not generate an error message --- is that a sign it's not 
>>> loaded?
>>>
>>>
>>> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:

 I'm working with Jann -- attached is our pom file (we call the jar 
 my-cas -- which is reflected in the URLs).

 It does not look like the JSON file is loaded -- I don't think it's pom 
 related --- but at the moment we are both stumped so anything goes.

 2018-05-14 20:23:17,715 WARN 
 [org.apereo.cas.services.web.ServiceThemeResolver] - >>> service 
 is found to match 
 [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
 http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
  
 or service access is disallowed. Using default theme [cas-theme-default]>

 On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:
>
>
> Attached is my 'cas.properties' file ---  in case I may be missing 
> something there (very likely)
>
>
> On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>>

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Va Sja]

What about 5.3.x? :-D

Am Dienstag, 15. Mai 2018 00:47:36 UTC+2 schrieb Man H:
>
>
> where are these pointing to:
>
> cas.serviceRegistry.json.location for 5.2.x 
> or 
> cas.serviceRegistry.config.location for 5.1.x
>
> 2018-05-14 19:41 GMT-03:00 Jann Malenkoff  >:
>
>> FYI --- the following appears in 'catalina.out' when attempting to access 
>> 'http://localhost:8080/cas-management/manage.html,'.
>>
>> 2018-05-14 15:39:09,152 WARN 
>> [org.apereo.cas.services.web.ServiceThemeResolver] - > is found to match 
>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=
>> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>  
>> or service access is disallowed. Using default theme [cas-theme-default]>
>>
>>
>> On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
>>>
>>> Hi Richard:
>>>
>>> I have the following in 'cas.properties':
>>>
>>> cas.serviceRegistry.initFromJson=true
>>>
>>> Is that correct to enable the first read from JSON? I have been staring 
>>> at the screen for so long and begining to doubt myself w.r.t true/false 
>>> flags.
>>>
>>> On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:

 Do you have initialization on from JSON? Not sure if it will use your 
 file or just the defaults. Either way, it should get you into the manager. 
 Then you configure the manager service, and turn that property off.

 # Auto-initialize the registry from default JSON service definitions
 # cas.serviceRegistry.initFromJson=false



 On 05/14/2018 05:13 PM, Jann Malenkoff wrote:

 Hi All:

 I'm trying to get the 'http://localhost:8080/cas-management/manage.html' 
 loaded up --- but hitting the error message: 
 ' 
 Application Not Authorized to Use CAS 

 The services registry of CAS is empty and has no service definitions. 
 Applications that wish to authenticate with CAS must explicitly be defined 
 in the services registry.'


 I am hoping to have a JPA service registry --- and have configured the 
 dependencies below in the 'cas-overlay-template' pom.xml.


 To enable the access to '
 http://localhost:8080/cas-management/manage.html, I have added  the 
 JASON entry as below --- but do not see it in the database table 
 REGEXREGISTEREDSERVICE (I have cas.serviceRegistry.config.location:
 file:/etc/cas/services in 'cas.properties).


 What could I have missed (or more likely misunderstood)?


 *JSON File in /etc/cas/services (copied -- slightly adjusted -- from an 
 earlier post):*

 {
   /*
* Wildcard service definition that applies to any https or imaps url.
* Do not use this definition in a production environment.
*/
   "@class" :
 "org.apereo.cas.services.RegexRegisteredService",
   "serviceId" : "^(http)://.*",
   "name" :  "HTTP wildcard",
   "id" :20180514,
   "evaluationOrder" :   9
 }


 *pom.xml -- for cas-overlay-template*

 
 
 org.apereo.cas
 
 cas-server-webapp${app.server}
 ${cas.version}
 war
 runtime
 
 
 org.apereo.cas
 
 cas-server-support-json-service-registry
 ${cas.version}
 
 
 org.apereo.cas
 cas-server-support-ldap
 ${cas.version}
 
 
 org.apereo.cas
 
 cas-server-support-jpa-service-registry
 ${cas.version}
 
 
 org.apereo.cas
 
 cas-server-support-jpa-ticket-registry
 ${cas.version}
 
 
 org.apereo.cas
 
 cas-server-support-jdbc-drivers
 ${cas.version}
 
 
 com.oracle
 ojdbc7.jar
 12.1.0.1
 
 
 org.apereo.cas
 cas-server-support-saml
 ${cas.version}
 
 
 org.apereo.cas
 cas-server-support-duo
 ${cas.version}
 
 
   

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[abdellhak tlili]

please can you share with me your LDAP configuration , exactly the 
modification of the file  "cas.properties" modification ,
have you modfied  some classes  in the overlay.?
 thanks alot

Le lundi 3 septembre 2018 03:21:33 UTC+2, 党田力 a écrit :
>
> But 5.1.9 works.
> Why?
>
> 在 2018年8月31日星期五 UTC+8下午9:46:17，Francois Campbell写道：
>>
>> Hi.
>>
>> I believe only one of the two should be in the pom.xml file at a time.
>> 
>> Regards
>> *Francois Campbell*
>> Teaching and Learning Product Lead
>>
>>
>>
>>
>>
>>
>> On Fri, 31 Aug 2018 at 13:05, 党田力  wrote:
>>
>>> I had test on 5.2.6 adn 5.2.7 version
>>> Only append `cas-server-support-json-service-registry` to pom.xml, the '
>>> cas.serviceRegistry.initFromJson=true' is worked.
>>> Only append `cas-server-support-jpa-service-registry` to pom.xml, the 
>>> database is worked.
>>> But I append both them, the services defined in json is not loaded.
>>>
>>> On 5.1.9 version works.
>>>
>>>
>>> 在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：

 Lionel and Jann,

 Did you ever have the JSON service registry working? If not, I 
 recommend that you take all the JPA stuff out of pom.xml and 
 cas.properties 
 and get that working correctly first, so that you're only trying to debug 
 one thing at a time. Once you have the JSON service registry working 
 correctly, for both the main server and the management webapp, then it's 
 time to move things to JPA.

 The basic steps for moving to JPA *should* be this:

 1. REMOVE the "cas-server-support-json-service-registry" dependency 
 from pom.xml (server and management webapp)

 2. Add the "cas-server-support-jpa-service-registry" dependency and 
 whatever other dependencies go with it to pom.xml (server and management 
 webapp)

 3. Rebuild the server and management webapp

 4. In the server's cas.properties file, include BOTH of these lines:

 cas.serviceRegistry.json.location: file:/etc/cas/services
 cas.serviceRegistry.initFromJson:  true


 The first line should already be there (since before you start these 
 steps you're using the JSON service registry), but you must add the second 
 line.

 5. Add all the lines you need to configure the JPA service registry to 
 the server's cas.properties file.

 6. Start the CAS server (do not start the management webapp). You 
 should see it load the services from the JSON files (again, this should 
 already be working before you start) and then it will magically save them 
 into the JPA registry.

 7. Shut the server down.

 8. Check the database to see that the services actually got loaded 
 there. If not, this is where you need to start debugging. And the first 
 step of that would be setting the log level to "debug" in log4j2.xml, and 
 adding whatever Logger configuration you need to make the Oracle JDBC 
 library log for you as well.

 Once you've got the services loaded into the database

 9. Remove the "cas.serviceRegistry.json.location" and 
 "cas.serviceRegistry.initFromJson" properties from the server's 
 cas.properties file.

 10. Remove the "cas.serviceRegistry.json.location" property from, and 
 add all the JPA properties to, the management webapp's 
 management.properties file.

 At least, that's the procedure I followed to get the MongoDB service 
 registry working (see 
 https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
  
 I've not used the JPA stuff at all, so no guarantees, but I don't see why 
 it should be any different.

 --Dave


 --

 DAVID A. CURRY, CISSP
 *DIRECTOR OF INFORMATION SECURITY*
 INFORMATION TECHNOLOGY

 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
 +1 212 229-5300 x4728 • david.cu...@newschool.edu

 [image: The New School]

 On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  
 wrote:

> Changing in "cas.properties"  
> 'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
> 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'
>
> The above does not generate an error message --- is that a sign it's 
> not loaded?
>
>
> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
>>
>> I'm working with Jann -- attached is our pom file (we call the jar 
>> my-cas -- which is reflected in the URLs).
>>
>> It does not look like the JSON file is loaded -- I don't think it's 
>> pom related --- but at the moment we are both stumped so anything goes.
>>
>> 2018-05-14 20:23:17,715 WARN 
>> [org.apereo.cas.services.web.ServiceThemeResolver] - > service 
>> is found to match 
>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
>> 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[abdellhak tlili]

please can you share with me your LDAP configuration , exactly the 
modification of the file  "cas.properties" modification ,
have you modfied  some classes  in the overlay.?
 thanks alot

Le lundi 3 septembre 2018 03:21:33 UTC+2, 党田力 a écrit :
>
> But 5.1.9 works.
> Why?
>
> 在 2018年8月31日星期五 UTC+8下午9:46:17，Francois Campbell写道：
>>
>> Hi.
>>
>> I believe only one of the two should be in the pom.xml file at a time.
>> 
>> Regards
>> *Francois Campbell*
>> Teaching and Learning Product Lead
>>
>>
>>
>>
>>
>>
>> On Fri, 31 Aug 2018 at 13:05, 党田力  wrote:
>>
>>> I had test on 5.2.6 adn 5.2.7 version
>>> Only append `cas-server-support-json-service-registry` to pom.xml, the '
>>> cas.serviceRegistry.initFromJson=true' is worked.
>>> Only append `cas-server-support-jpa-service-registry` to pom.xml, the 
>>> database is worked.
>>> But I append both them, the services defined in json is not loaded.
>>>
>>> On 5.1.9 version works.
>>>
>>>
>>> 在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：

 Lionel and Jann,

 Did you ever have the JSON service registry working? If not, I 
 recommend that you take all the JPA stuff out of pom.xml and 
 cas.properties 
 and get that working correctly first, so that you're only trying to debug 
 one thing at a time. Once you have the JSON service registry working 
 correctly, for both the main server and the management webapp, then it's 
 time to move things to JPA.

 The basic steps for moving to JPA *should* be this:

 1. REMOVE the "cas-server-support-json-service-registry" dependency 
 from pom.xml (server and management webapp)

 2. Add the "cas-server-support-jpa-service-registry" dependency and 
 whatever other dependencies go with it to pom.xml (server and management 
 webapp)

 3. Rebuild the server and management webapp

 4. In the server's cas.properties file, include BOTH of these lines:

 cas.serviceRegistry.json.location: file:/etc/cas/services
 cas.serviceRegistry.initFromJson:  true


 The first line should already be there (since before you start these 
 steps you're using the JSON service registry), but you must add the second 
 line.

 5. Add all the lines you need to configure the JPA service registry to 
 the server's cas.properties file.

 6. Start the CAS server (do not start the management webapp). You 
 should see it load the services from the JSON files (again, this should 
 already be working before you start) and then it will magically save them 
 into the JPA registry.

 7. Shut the server down.

 8. Check the database to see that the services actually got loaded 
 there. If not, this is where you need to start debugging. And the first 
 step of that would be setting the log level to "debug" in log4j2.xml, and 
 adding whatever Logger configuration you need to make the Oracle JDBC 
 library log for you as well.

 Once you've got the services loaded into the database

 9. Remove the "cas.serviceRegistry.json.location" and 
 "cas.serviceRegistry.initFromJson" properties from the server's 
 cas.properties file.

 10. Remove the "cas.serviceRegistry.json.location" property from, and 
 add all the JPA properties to, the management webapp's 
 management.properties file.

 At least, that's the procedure I followed to get the MongoDB service 
 registry working (see 
 https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
  
 I've not used the JPA stuff at all, so no guarantees, but I don't see why 
 it should be any different.

 --Dave


 --

 DAVID A. CURRY, CISSP
 *DIRECTOR OF INFORMATION SECURITY*
 INFORMATION TECHNOLOGY

 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
 +1 212 229-5300 x4728 • david.cu...@newschool.edu

 [image: The New School]

 On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  
 wrote:

> Changing in "cas.properties"  
> 'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
> 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'
>
> The above does not generate an error message --- is that a sign it's 
> not loaded?
>
>
> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
>>
>> I'm working with Jann -- attached is our pom file (we call the jar 
>> my-cas -- which is reflected in the URLs).
>>
>> It does not look like the JSON file is loaded -- I don't think it's 
>> pom related --- but at the moment we are both stumped so anything goes.
>>
>> 2018-05-14 20:23:17,715 WARN 
>> [org.apereo.cas.services.web.ServiceThemeResolver] - > service 
>> is found to match 
>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
>> 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[党田力]

But 5.1.9 works.
Why?

在 2018年8月31日星期五 UTC+8下午9:46:17，Francois Campbell写道：
>
> Hi.
>
> I believe only one of the two should be in the pom.xml file at a time.
> 
> Regards
> *Francois Campbell*
> Teaching and Learning Product Lead
>
>
>
>
>
>
> On Fri, 31 Aug 2018 at 13:05, 党田力 > 
> wrote:
>
>> I had test on 5.2.6 adn 5.2.7 version
>> Only append `cas-server-support-json-service-registry` to pom.xml, the '
>> cas.serviceRegistry.initFromJson=true' is worked.
>> Only append `cas-server-support-jpa-service-registry` to pom.xml, the 
>> database is worked.
>> But I append both them, the services defined in json is not loaded.
>>
>> On 5.1.9 version works.
>>
>>
>> 在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：
>>>
>>> Lionel and Jann,
>>>
>>> Did you ever have the JSON service registry working? If not, I recommend 
>>> that you take all the JPA stuff out of pom.xml and cas.properties and get 
>>> that working correctly first, so that you're only trying to debug one thing 
>>> at a time. Once you have the JSON service registry working correctly, for 
>>> both the main server and the management webapp, then it's time to move 
>>> things to JPA.
>>>
>>> The basic steps for moving to JPA *should* be this:
>>>
>>> 1. REMOVE the "cas-server-support-json-service-registry" dependency from 
>>> pom.xml (server and management webapp)
>>>
>>> 2. Add the "cas-server-support-jpa-service-registry" dependency and 
>>> whatever other dependencies go with it to pom.xml (server and management 
>>> webapp)
>>>
>>> 3. Rebuild the server and management webapp
>>>
>>> 4. In the server's cas.properties file, include BOTH of these lines:
>>>
>>> cas.serviceRegistry.json.location: file:/etc/cas/services
>>> cas.serviceRegistry.initFromJson:  true
>>>
>>>
>>> The first line should already be there (since before you start these 
>>> steps you're using the JSON service registry), but you must add the second 
>>> line.
>>>
>>> 5. Add all the lines you need to configure the JPA service registry to 
>>> the server's cas.properties file.
>>>
>>> 6. Start the CAS server (do not start the management webapp). You should 
>>> see it load the services from the JSON files (again, this should already be 
>>> working before you start) and then it will magically save them into the JPA 
>>> registry.
>>>
>>> 7. Shut the server down.
>>>
>>> 8. Check the database to see that the services actually got loaded 
>>> there. If not, this is where you need to start debugging. And the first 
>>> step of that would be setting the log level to "debug" in log4j2.xml, and 
>>> adding whatever Logger configuration you need to make the Oracle JDBC 
>>> library log for you as well.
>>>
>>> Once you've got the services loaded into the database
>>>
>>> 9. Remove the "cas.serviceRegistry.json.location" and 
>>> "cas.serviceRegistry.initFromJson" properties from the server's 
>>> cas.properties file.
>>>
>>> 10. Remove the "cas.serviceRegistry.json.location" property from, and 
>>> add all the JPA properties to, the management webapp's 
>>> management.properties file.
>>>
>>> At least, that's the procedure I followed to get the MongoDB service 
>>> registry working (see 
>>> https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
>>>  
>>> I've not used the JPA stuff at all, so no guarantees, but I don't see why 
>>> it should be any different.
>>>
>>> --Dave
>>>
>>>
>>> --
>>>
>>> DAVID A. CURRY, CISSP
>>> *DIRECTOR OF INFORMATION SECURITY*
>>> INFORMATION TECHNOLOGY
>>>
>>> 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
>>> +1 212 229-5300 x4728 • david.cu...@newschool.edu
>>>
>>> [image: The New School]
>>>
>>> On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  
>>> wrote:
>>>
 Changing in "cas.properties"  
 'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'

 The above does not generate an error message --- is that a sign it's 
 not loaded?


 On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
>
> I'm working with Jann -- attached is our pom file (we call the jar 
> my-cas -- which is reflected in the URLs).
>
> It does not look like the JSON file is loaded -- I don't think it's 
> pom related --- but at the moment we are both stumped so anything goes.
>
> 2018-05-14 20:23:17,715 WARN 
> [org.apereo.cas.services.web.ServiceThemeResolver] -  service 
> is found to match 
> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>  
> or service access is disallowed. Using default theme [cas-theme-default]>
>
> On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:
>>
>>
>> Attached is my 'cas.properties' file 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Francois Campbell]

Hi.

I believe only one of the two should be in the pom.xml file at a time.

Regards
*Francois Campbell*
Teaching and Learning Product Lead






On Fri, 31 Aug 2018 at 13:05, 党田力  wrote:

> I had test on 5.2.6 adn 5.2.7 version
> Only append `cas-server-support-json-service-registry` to pom.xml, the '
> cas.serviceRegistry.initFromJson=true' is worked.
> Only append `cas-server-support-jpa-service-registry` to pom.xml, the
> database is worked.
> But I append both them, the services defined in json is not loaded.
>
> On 5.1.9 version works.
>
>
> 在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：
>>
>> Lionel and Jann,
>>
>> Did you ever have the JSON service registry working? If not, I recommend
>> that you take all the JPA stuff out of pom.xml and cas.properties and get
>> that working correctly first, so that you're only trying to debug one thing
>> at a time. Once you have the JSON service registry working correctly, for
>> both the main server and the management webapp, then it's time to move
>> things to JPA.
>>
>> The basic steps for moving to JPA *should* be this:
>>
>> 1. REMOVE the "cas-server-support-json-service-registry" dependency from
>> pom.xml (server and management webapp)
>>
>> 2. Add the "cas-server-support-jpa-service-registry" dependency and
>> whatever other dependencies go with it to pom.xml (server and management
>> webapp)
>>
>> 3. Rebuild the server and management webapp
>>
>> 4. In the server's cas.properties file, include BOTH of these lines:
>>
>> cas.serviceRegistry.json.location: file:/etc/cas/services
>> cas.serviceRegistry.initFromJson:  true
>>
>>
>> The first line should already be there (since before you start these
>> steps you're using the JSON service registry), but you must add the second
>> line.
>>
>> 5. Add all the lines you need to configure the JPA service registry to
>> the server's cas.properties file.
>>
>> 6. Start the CAS server (do not start the management webapp). You should
>> see it load the services from the JSON files (again, this should already be
>> working before you start) and then it will magically save them into the JPA
>> registry.
>>
>> 7. Shut the server down.
>>
>> 8. Check the database to see that the services actually got loaded there.
>> If not, this is where you need to start debugging. And the first step of
>> that would be setting the log level to "debug" in log4j2.xml, and adding
>> whatever Logger configuration you need to make the Oracle JDBC library log
>> for you as well.
>>
>> Once you've got the services loaded into the database
>>
>> 9. Remove the "cas.serviceRegistry.json.location" and
>> "cas.serviceRegistry.initFromJson" properties from the server's
>> cas.properties file.
>>
>> 10. Remove the "cas.serviceRegistry.json.location" property from, and add
>> all the JPA properties to, the management webapp's management.properties
>> file.
>>
>> At least, that's the procedure I followed to get the MongoDB service
>> registry working (see
>> https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
>> I've not used the JPA stuff at all, so no guarantees, but I don't see why
>> it should be any different.
>>
>> --Dave
>>
>>
>> --
>>
>> DAVID A. CURRY, CISSP
>> *DIRECTOR OF INFORMATION SECURITY*
>> INFORMATION TECHNOLOGY
>>
>> 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
>> +1 212 229-5300 x4728 • david.cu...@newschool.edu
>>
>> [image: The New School]
>>
>> On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel 
>> wrote:
>>
>>> Changing in "cas.properties"
>>> 'cas.serviceRegistry.json.location:file:/etc/cas/services' to
>>> 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'
>>>
>>> The above does not generate an error message --- is that a sign it's not
>>> loaded?
>>>
>>>
>>> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:

 I'm working with Jann -- attached is our pom file (we call the jar
 my-cas -- which is reflected in the URLs).

 It does not look like the JSON file is loaded -- I don't think it's pom
 related --- but at the moment we are both stumped so anything goes.

 2018-05-14 20:23:17,715 WARN
 [org.apereo.cas.services.web.ServiceThemeResolver] - >>> is found to match
 [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf
 [id=
 http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
 or service access is disallowed. Using default theme [cas-theme-default]>

 On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:
>
>
> Attached is my 'cas.properties' file ---  in case I may be missing
> something there (very likely)
>
>
> On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>>
>> I had a minor Eureka moment --- but it came to fraught (partially).
>>
>> I has a typo in the 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[党田力]

I debug the JsonServiceRegistryConfiguration, the class is not loaded.
Then I change the version of spring from 1.5.12 to 1.5.15, nothing changes.

在 2018年8月31日星期五 UTC+8下午7:05:02，党田力写道：
>
> I had test on 5.2.6 adn 5.2.7 version
> Only append `cas-server-support-json-service-registry` to pom.xml, the '
> cas.serviceRegistry.initFromJson=true' is worked.
> Only append `cas-server-support-jpa-service-registry` to pom.xml, the 
> database is worked.
> But I append both them, the services defined in json is not loaded.
>
> On 5.1.9 version works.
>
>
> 在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：
>>
>> Lionel and Jann,
>>
>> Did you ever have the JSON service registry working? If not, I recommend 
>> that you take all the JPA stuff out of pom.xml and cas.properties and get 
>> that working correctly first, so that you're only trying to debug one thing 
>> at a time. Once you have the JSON service registry working correctly, for 
>> both the main server and the management webapp, then it's time to move 
>> things to JPA.
>>
>> The basic steps for moving to JPA *should* be this:
>>
>> 1. REMOVE the "cas-server-support-json-service-registry" dependency from 
>> pom.xml (server and management webapp)
>>
>> 2. Add the "cas-server-support-jpa-service-registry" dependency and 
>> whatever other dependencies go with it to pom.xml (server and management 
>> webapp)
>>
>> 3. Rebuild the server and management webapp
>>
>> 4. In the server's cas.properties file, include BOTH of these lines:
>>
>> cas.serviceRegistry.json.location: file:/etc/cas/services
>> cas.serviceRegistry.initFromJson:  true
>>
>>
>> The first line should already be there (since before you start these 
>> steps you're using the JSON service registry), but you must add the second 
>> line.
>>
>> 5. Add all the lines you need to configure the JPA service registry to 
>> the server's cas.properties file.
>>
>> 6. Start the CAS server (do not start the management webapp). You should 
>> see it load the services from the JSON files (again, this should already be 
>> working before you start) and then it will magically save them into the JPA 
>> registry.
>>
>> 7. Shut the server down.
>>
>> 8. Check the database to see that the services actually got loaded there. 
>> If not, this is where you need to start debugging. And the first step of 
>> that would be setting the log level to "debug" in log4j2.xml, and adding 
>> whatever Logger configuration you need to make the Oracle JDBC library log 
>> for you as well.
>>
>> Once you've got the services loaded into the database
>>
>> 9. Remove the "cas.serviceRegistry.json.location" and 
>> "cas.serviceRegistry.initFromJson" properties from the server's 
>> cas.properties file.
>>
>> 10. Remove the "cas.serviceRegistry.json.location" property from, and add 
>> all the JPA properties to, the management webapp's management.properties 
>> file.
>>
>> At least, that's the procedure I followed to get the MongoDB service 
>> registry working (see 
>> https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
>>  
>> I've not used the JPA stuff at all, so no guarantees, but I don't see why 
>> it should be any different.
>>
>> --Dave
>>
>>
>> --
>>
>> DAVID A. CURRY, CISSP
>> *DIRECTOR OF INFORMATION SECURITY*
>> INFORMATION TECHNOLOGY
>>
>> 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
>> +1 212 229-5300 x4728 • david.cu...@newschool.edu
>>
>> [image: The New School]
>>
>> On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  
>> wrote:
>>
>>> Changing in "cas.properties"  
>>> 'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
>>> 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'
>>>
>>> The above does not generate an error message --- is that a sign it's not 
>>> loaded?
>>>
>>>
>>> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:

 I'm working with Jann -- attached is our pom file (we call the jar 
 my-cas -- which is reflected in the URLs).

 It does not look like the JSON file is loaded -- I don't think it's pom 
 related --- but at the moment we are both stumped so anything goes.

 2018-05-14 20:23:17,715 WARN 
 [org.apereo.cas.services.web.ServiceThemeResolver] - >>> service 
 is found to match 
 [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
 http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
  
 or service access is disallowed. Using default theme [cas-theme-default]>

 On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:
>
>
> Attached is my 'cas.properties' file ---  in case I may be missing 
> something there (very likely)
>
>
> On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>>
>> I had a minor Eureka moment --- but it came to fraught 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[党田力]

I had test on 5.2.6 adn 5.2.7 version
Only append `cas-server-support-json-service-registry` to pom.xml, the '
cas.serviceRegistry.initFromJson=true' is worked.
Only append `cas-server-support-jpa-service-registry` to pom.xml, the 
database is worked.
But I append both them, the services defined in json is not loaded.

On 5.1.9 version works.


在 2018年5月15日星期二 UTC+8下午8:15:55，David Curry写道：
>
> Lionel and Jann,
>
> Did you ever have the JSON service registry working? If not, I recommend 
> that you take all the JPA stuff out of pom.xml and cas.properties and get 
> that working correctly first, so that you're only trying to debug one thing 
> at a time. Once you have the JSON service registry working correctly, for 
> both the main server and the management webapp, then it's time to move 
> things to JPA.
>
> The basic steps for moving to JPA *should* be this:
>
> 1. REMOVE the "cas-server-support-json-service-registry" dependency from 
> pom.xml (server and management webapp)
>
> 2. Add the "cas-server-support-jpa-service-registry" dependency and 
> whatever other dependencies go with it to pom.xml (server and management 
> webapp)
>
> 3. Rebuild the server and management webapp
>
> 4. In the server's cas.properties file, include BOTH of these lines:
>
> cas.serviceRegistry.json.location: file:/etc/cas/services
> cas.serviceRegistry.initFromJson:  true
>
>
> The first line should already be there (since before you start these steps 
> you're using the JSON service registry), but you must add the second line.
>
> 5. Add all the lines you need to configure the JPA service registry to the 
> server's cas.properties file.
>
> 6. Start the CAS server (do not start the management webapp). You should 
> see it load the services from the JSON files (again, this should already be 
> working before you start) and then it will magically save them into the JPA 
> registry.
>
> 7. Shut the server down.
>
> 8. Check the database to see that the services actually got loaded there. 
> If not, this is where you need to start debugging. And the first step of 
> that would be setting the log level to "debug" in log4j2.xml, and adding 
> whatever Logger configuration you need to make the Oracle JDBC library log 
> for you as well.
>
> Once you've got the services loaded into the database
>
> 9. Remove the "cas.serviceRegistry.json.location" and 
> "cas.serviceRegistry.initFromJson" properties from the server's 
> cas.properties file.
>
> 10. Remove the "cas.serviceRegistry.json.location" property from, and add 
> all the JPA properties to, the management webapp's management.properties 
> file.
>
> At least, that's the procedure I followed to get the MongoDB service 
> registry working (see 
> https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
>  
> I've not used the JPA stuff at all, so no guarantees, but I don't see why 
> it should be any different.
>
> --Dave
>
>
> --
>
> DAVID A. CURRY, CISSP
> *DIRECTOR OF INFORMATION SECURITY*
> INFORMATION TECHNOLOGY
>
> 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
> +1 212 229-5300 x4728 • david.cu...@newschool.edu 
>
> [image: The New School]
>
> On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  > wrote:
>
>> Changing in "cas.properties"  
>> 'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
>> 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'
>>
>> The above does not generate an error message --- is that a sign it's not 
>> loaded?
>>
>>
>> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
>>>
>>> I'm working with Jann -- attached is our pom file (we call the jar 
>>> my-cas -- which is reflected in the URLs).
>>>
>>> It does not look like the JSON file is loaded -- I don't think it's pom 
>>> related --- but at the moment we are both stumped so anything goes.
>>>
>>> 2018-05-14 20:23:17,715 WARN 
>>> [org.apereo.cas.services.web.ServiceThemeResolver] - >> is found to match 
>>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
>>> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>>  
>>> or service access is disallowed. Using default theme [cas-theme-default]>
>>>
>>> On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:


 Attached is my 'cas.properties' file ---  in case I may be missing 
 something there (very likely)


 On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>
> I had a minor Eureka moment --- but it came to fraught (partially).
>
> I has a typo in the 'cas.properties' file: 
> cas.serviceRegistry.json.location:file:/etc/cas/service
>
> i,e, 'service' instead of 'services' --- corrected now (validated that 
> the json files are in '/etc/cas/services').
>
> But still no-go...any ideas will be matched by the maximum Karma 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Jann Malenkoff]

Hi David:

You Sir --- are a gentleman and a scholar.

Very much appreciated from both of us.

Working exactly as you have outlined.

Please accept out utmost gratitude. 

On Tuesday, May 15, 2018 at 5:15:55 AM UTC-7, David Curry wrote:
>
> Lionel and Jann,
>
> Did you ever have the JSON service registry working? If not, I recommend 
> that you take all the JPA stuff out of pom.xml and cas.properties and get 
> that working correctly first, so that you're only trying to debug one thing 
> at a time. Once you have the JSON service registry working correctly, for 
> both the main server and the management webapp, then it's time to move 
> things to JPA.
>
> The basic steps for moving to JPA *should* be this:
>
> 1. REMOVE the "cas-server-support-json-service-registry" dependency from 
> pom.xml (server and management webapp)
>
> 2. Add the "cas-server-support-jpa-service-registry" dependency and 
> whatever other dependencies go with it to pom.xml (server and management 
> webapp)
>
> 3. Rebuild the server and management webapp
>
> 4. In the server's cas.properties file, include BOTH of these lines:
>
> cas.serviceRegistry.json.location: file:/etc/cas/services
> cas.serviceRegistry.initFromJson:  true
>
>
> The first line should already be there (since before you start these steps 
> you're using the JSON service registry), but you must add the second line.
>
> 5. Add all the lines you need to configure the JPA service registry to the 
> server's cas.properties file.
>
> 6. Start the CAS server (do not start the management webapp). You should 
> see it load the services from the JSON files (again, this should already be 
> working before you start) and then it will magically save them into the JPA 
> registry.
>
> 7. Shut the server down.
>
> 8. Check the database to see that the services actually got loaded there. 
> If not, this is where you need to start debugging. And the first step of 
> that would be setting the log level to "debug" in log4j2.xml, and adding 
> whatever Logger configuration you need to make the Oracle JDBC library log 
> for you as well.
>
> Once you've got the services loaded into the database
>
> 9. Remove the "cas.serviceRegistry.json.location" and 
> "cas.serviceRegistry.initFromJson" properties from the server's 
> cas.properties file.
>
> 10. Remove the "cas.serviceRegistry.json.location" property from, and add 
> all the JPA properties to, the management webapp's management.properties 
> file.
>
> At least, that's the procedure I followed to get the MongoDB service 
> registry working (see 
> https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
>  
> I've not used the JPA stuff at all, so no guarantees, but I don't see why 
> it should be any different.
>
> --Dave
>
>
> --
>
> DAVID A. CURRY, CISSP
> *DIRECTOR OF INFORMATION SECURITY*
> INFORMATION TECHNOLOGY
>
> 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
> +1 212 229-5300 x4728 • david.cu...@newschool.edu 
>
> [image: The New School]
>
> On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel  > wrote:
>
>> Changing in "cas.properties"  
>> 'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
>> 'cas.serviceRegistry.json.location:foobar:/etc/cas/services'
>>
>> The above does not generate an error message --- is that a sign it's not 
>> loaded?
>>
>>
>> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
>>>
>>> I'm working with Jann -- attached is our pom file (we call the jar 
>>> my-cas -- which is reflected in the URLs).
>>>
>>> It does not look like the JSON file is loaded -- I don't think it's pom 
>>> related --- but at the moment we are both stumped so anything goes.
>>>
>>> 2018-05-14 20:23:17,715 WARN 
>>> [org.apereo.cas.services.web.ServiceThemeResolver] - >> is found to match 
>>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
>>> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>>  
>>> or service access is disallowed. Using default theme [cas-theme-default]>
>>>
>>> On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:


 Attached is my 'cas.properties' file ---  in case I may be missing 
 something there (very likely)


 On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>
> I had a minor Eureka moment --- but it came to fraught (partially).
>
> I has a typo in the 'cas.properties' file: 
> cas.serviceRegistry.json.location:file:/etc/cas/service
>
> i,e, 'service' instead of 'services' --- corrected now (validated that 
> the json files are in '/etc/cas/services').
>
> But still no-go...any ideas will be matched by the maximum Karma I 
> can provide.
>
> On Monday, May 14, 2018 at 4:16:39 PM UTC-7, Jann Malenkoff wrote:
>>
>> I'm on 5.2.4 --- 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[David Curry]

Lionel and Jann,

Did you ever have the JSON service registry working? If not, I recommend
that you take all the JPA stuff out of pom.xml and cas.properties and get
that working correctly first, so that you're only trying to debug one thing
at a time. Once you have the JSON service registry working correctly, for
both the main server and the management webapp, then it's time to move
things to JPA.

The basic steps for moving to JPA *should* be this:

1. REMOVE the "cas-server-support-json-service-registry" dependency from
pom.xml (server and management webapp)

2. Add the "cas-server-support-jpa-service-registry" dependency and
whatever other dependencies go with it to pom.xml (server and management
webapp)

3. Rebuild the server and management webapp

4. In the server's cas.properties file, include BOTH of these lines:

cas.serviceRegistry.json.location: file:/etc/cas/services
cas.serviceRegistry.initFromJson:  true


The first line should already be there (since before you start these steps
you're using the JSON service registry), but you must add the second line.

5. Add all the lines you need to configure the JPA service registry to the
server's cas.properties file.

6. Start the CAS server (do not start the management webapp). You should
see it load the services from the JSON files (again, this should already be
working before you start) and then it will magically save them into the JPA
registry.

7. Shut the server down.

8. Check the database to see that the services actually got loaded there.
If not, this is where you need to start debugging. And the first step of
that would be setting the log level to "debug" in log4j2.xml, and adding
whatever Logger configuration you need to make the Oracle JDBC library log
for you as well.

Once you've got the services loaded into the database

9. Remove the "cas.serviceRegistry.json.location" and
"cas.serviceRegistry.initFromJson" properties from the server's
cas.properties file.

10. Remove the "cas.serviceRegistry.json.location" property from, and add
all the JPA properties to, the management webapp's management.properties
file.

At least, that's the procedure I followed to get the MongoDB service
registry working (see
https://dacurry-tns.github.io/deploying-apereo-cas/high-avail_service-registry_overview.html).
I've not used the JPA stuff at all, so no guarantees, but I don't see why
it should be any different.

--Dave


--

DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
INFORMATION TECHNOLOGY

71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300 x4728 • david.cu...@newschool.edu

[image: The New School]

On Tue, May 15, 2018 at 12:14 AM, Lionel Samuel 
wrote:

> Changing in "cas.properties"  'cas.serviceRegistry.json.
> location:file:/etc/cas/services' to 'cas.serviceRegistry.json.
> location:foobar:/etc/cas/services'
>
> The above does not generate an error message --- is that a sign it's not
> loaded?
>
>
> On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
>>
>> I'm working with Jann -- attached is our pom file (we call the jar my-cas
>> -- which is reflected in the URLs).
>>
>> It does not look like the JSON file is loaded -- I don't think it's pom
>> related --- but at the moment we are both stumped so anything goes.
>>
>> 2018-05-14 20:23:17,715 WARN 
>> [org.apereo.cas.services.web.ServiceThemeResolver]
>> - > .principal.SimpleWebApplicationServiceImpl@330c1ecf[id=http:
>> //localhost:8080/cas-management/manage.html,originalUrl=http://localhost:
>> 8080/cas-management/manage.html,artifactId=,principal=,
>> loggedOutAlready=false,format=XML]] or service access is disallowed.
>> Using default theme [cas-theme-default]>
>>
>> On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:
>>>
>>>
>>> Attached is my 'cas.properties' file ---  in case I may be missing
>>> something there (very likely)
>>>
>>>
>>> On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:

 I had a minor Eureka moment --- but it came to fraught (partially).

 I has a typo in the 'cas.properties' file:
 cas.serviceRegistry.json.location:file:/etc/cas/service

 i,e, 'service' instead of 'services' --- corrected now (validated that
 the json files are in '/etc/cas/services').

 But still no-go...any ideas will be matched by the maximum Karma I
 can provide.

 On Monday, May 14, 2018 at 4:16:39 PM UTC-7, Jann Malenkoff wrote:
>
> I'm on 5.2.4 --- I had earlier the 5.1 (i.e. cas.serviceRegistry
> .config.location) in 'cas.properties'--- now, updated to below (the
> 5.2.x version)
>
> cas.serviceRegistry.json.location:file:/etc/cas/service
> cas.serviceRegistry.initFromJson=true
>
> Still getting error below:
>
> 2018-05-14 16:11:41,016 WARN 
> [org.apereo.cas.services.web.ServiceThemeResolver]
> -  .principal.SimpleWebApplicationServiceImpl@3f670479[id=http:
> 

RE: [cas-user] Service Registry -- Getting the 1st Application Entered

[King, Robert]

Does the tomcat service have proper read rights to the json files and/or the 
/etc/cas/services/ directories?

From: cas-user@apereo.org [mailto:cas-user@apereo.org] On Behalf Of Jann 
Malenkoff
Sent: May-14-18 9:39 PM
To: CAS Community <cas-user@apereo.org>
Subject: Re: [cas-user] Service Registry -- Getting the 1st Application Entered

I had a minor Eureka moment --- but it came to fraught (partially).

I has a typo in the 'cas.properties' file: 
cas.serviceRegistry.json.location:file:/etc/cas/service

i,e, 'service' instead of 'services' --- corrected now (validated that the json 
files are in '/etc/cas/services').

But still no-go...any ideas will be matched by the maximum Karma I can 
provide.

On Monday, May 14, 2018 at 4:16:39 PM UTC-7, Jann Malenkoff wrote:
I'm on 5.2.4 --- I had earlier the 5.1 (i.e. 
cas.serviceRegistry.config.location) in 'cas.properties'--- now, updated to 
below (the 5.2.x version)

cas.serviceRegistry.json.location:file:/etc/cas/service
cas.serviceRegistry.initFromJson=true

Still getting error below:

2018-05-14 16:11:41,016 WARN [org.apereo.cas.services.web.ServiceThemeResolver] 
- http://localhost:8080/cas-management/manage.html,originalUrl=http://locahost:8080/cas-management/manage.html,artifactId=<http://localhost:8080/cas-management/manage.html,originalUrl=http:/locahost:8080/cas-management/manage.html,artifactId=>,principal=,loggedOutAlready=false,format=XML]]
 or service access is disallowed. Using default theme [cas-theme-default]>

Json file:

{
  "@class" :"org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(http)://.*",
  "name" :  "HTTP wildcard",
  "id" :20170905111650,
  "evaluationOrder" :   9
}

Have I missed anything else? Could there be something else in the logs that can 
give a clue (I have been hunting but may be missing it)?

On Monday, May 14, 2018 at 3:47:36 PM UTC-7, Manfredo Hopp wrote:

where are these pointing to:

cas.serviceRegistry.json.location for 5.2.x
or
cas.serviceRegistry.config.location for 5.1.x

2018-05-14 19:41 GMT-03:00 Jann Malenkoff 
<jannma...@gmail.com<mailto:jannma...@gmail.com>>:
FYI --- the following appears in 'catalina.out' when attempting to access 
'http://localhost:8080/cas-management/manage.html,'.

2018-05-14 15:39:09,152 WARN [org.apereo.cas.services.web.ServiceThemeResolver] 
- http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=<http://localhost:8080/cas-management/manage.html,originalUrl=http:/localhost:8080/cas-management/manage.html,artifactId=>,principal=,loggedOutAlready=false,format=XML]]
 or service access is disallowed. Using default theme [cas-theme-default]>


On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
Hi Richard:

I have the following in 'cas.properties':

cas.serviceRegistry.initFromJson=true

Is that correct to enable the first read from JSON? I have been staring at the 
screen for so long and begining to doubt myself w.r.t true/false flags.

On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:
Do you have initialization on from JSON? Not sure if it will use your file or 
just the defaults. Either way, it should get you into the manager. Then you 
configure the manager service, and turn that property off.



# Auto-initialize the registry from default JSON service definitions

# cas.serviceRegistry.initFromJson=false


On 05/14/2018 05:13 PM, Jann Malenkoff wrote:
Hi All:

I'm trying to get the 'http://localhost:8080/cas-management/manage.html' loaded 
up --- but hitting the error message:
'
Application Not Authorized to Use CAS

The services registry of CAS is empty and has no service definitions. 
Applications that wish to authenticate with CAS must explicitly be defined in 
the services registry.'



I am hoping to have a JPA service registry --- and have configured the 
dependencies below in the 'cas-overlay-template' pom.xml.



To enable the access to 'http://localhost:8080/cas-management/manage.html, I 
have added  the JASON entry as below --- but do not see it in the database 
table REGEXREGISTEREDSERVICE (I have cas.serviceRegistry.config.location:
file:/etc/cas/services in 'cas.properties).



What could I have missed (or more likely misunderstood)?



JSON File in /etc/cas/services (copied -- slightly adjusted -- from an earlier 
post):

{
  /*
   * Wildcard service definition that applies to any https or imaps url.
   * Do not use this definition in a production environment.
   */
  "@class" :"org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(http)://.*",
  "name" :  "HTTP wildcard",
  "id" :20180514,
  "evaluationOrder" :   9
}


pom

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Lionel Samuel]

Changing in "cas.properties"  
'cas.serviceRegistry.json.location:file:/etc/cas/services' to 
'cas.serviceRegistry.json.location:foobar:/etc/cas/services'

The above does not generate an error message --- is that a sign it's not 
loaded?

On Monday, May 14, 2018 at 8:25:37 PM UTC-7, Lionel Samuel wrote:
>
> I'm working with Jann -- attached is our pom file (we call the jar my-cas 
> -- which is reflected in the URLs).
>
> It does not look like the JSON file is loaded -- I don't think it's pom 
> related --- but at the moment we are both stumped so anything goes.
>
> 2018-05-14 20:23:17,715 WARN 
> [org.apereo.cas.services.web.ServiceThemeResolver] -  is found to match 
> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@330c1ecf[id=
> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>  
> or service access is disallowed. Using default theme [cas-theme-default]>
>
> On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:
>>
>>
>> Attached is my 'cas.properties' file ---  in case I may be missing 
>> something there (very likely)
>>
>>
>> On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>>>
>>> I had a minor Eureka moment --- but it came to fraught (partially).
>>>
>>> I has a typo in the 'cas.properties' file: 
>>> cas.serviceRegistry.json.location:file:/etc/cas/service
>>>
>>> i,e, 'service' instead of 'services' --- corrected now (validated that 
>>> the json files are in '/etc/cas/services').
>>>
>>> But still no-go...any ideas will be matched by the maximum Karma I 
>>> can provide.
>>>
>>> On Monday, May 14, 2018 at 4:16:39 PM UTC-7, Jann Malenkoff wrote:

 I'm on 5.2.4 --- I had earlier the 5.1 (i.e. 
 cas.serviceRegistry.config.location) 
 in 'cas.properties'--- now, updated to below (the 5.2.x version)

 cas.serviceRegistry.json.location:file:/etc/cas/service
 cas.serviceRegistry.initFromJson=true

 Still getting error below:

 2018-05-14 16:11:41,016 WARN 
 [org.apereo.cas.services.web.ServiceThemeResolver] - >>> service 
 is found to match 
 [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@3f670479[id=
 http://localhost:8080/cas-management/manage.html,originalUrl=http://locahost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
  
 or service access is disallowed. Using default theme [cas-theme-default]>

 Json file:

 {
   "@class" :
 "org.apereo.cas.services.RegexRegisteredService",
   "serviceId" : "^(http)://.*",
   "name" :  "HTTP wildcard",
   "id" :20170905111650,
   "evaluationOrder" :   9
 }

 Have I missed anything else? Could there be something else in the logs 
 that can give a clue (I have been hunting but may be missing it)?

 On Monday, May 14, 2018 at 3:47:36 PM UTC-7, Manfredo Hopp wrote:
>
>
> where are these pointing to:
>
> cas.serviceRegistry.json.location for 5.2.x 
> or 
> cas.serviceRegistry.config.location for 5.1.x
>
> 2018-05-14 19:41 GMT-03:00 Jann Malenkoff :
>
>> FYI --- the following appears in 'catalina.out' when attempting to 
>> access 'http://localhost:8080/cas-management/manage.html,'.
>>
>> 2018-05-14 15:39:09,152 WARN 
>> [org.apereo.cas.services.web.ServiceThemeResolver] - > service 
>> is found to match 
>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=
>> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>  
>> or service access is disallowed. Using default theme [cas-theme-default]>
>>
>>
>> On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
>>>
>>> Hi Richard:
>>>
>>> I have the following in 'cas.properties':
>>>
>>> cas.serviceRegistry.initFromJson=true
>>>
>>> Is that correct to enable the first read from JSON? I have been 
>>> staring at the screen for so long and begining to doubt myself w.r.t 
>>> true/false flags.
>>>
>>> On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:

 Do you have initialization on from JSON? Not sure if it will use 
 your file or just the defaults. Either way, it should get you into the 
 manager. Then you configure the manager service, and turn that 
 property off.

 # Auto-initialize the registry from default JSON service definitions
 # cas.serviceRegistry.initFromJson=false



 On 05/14/2018 05:13 PM, Jann Malenkoff wrote:

 Hi All:

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Lionel Samuel]

I'm working with Jann -- attached is our pom file (we call the jar my-cas 
-- which is reflected in the URLs).

It does not look like the JSON file is loaded -- I don't think it's pom 
related --- but at the moment we are both stumped so anything goes.

2018-05-14 20:23:17,715 WARN 
[org.apereo.cas.services.web.ServiceThemeResolver] - http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
 
or service access is disallowed. Using default theme [cas-theme-default]>

On Monday, May 14, 2018 at 5:42:35 PM UTC-7, Jann Malenkoff wrote:
>
>
> Attached is my 'cas.properties' file ---  in case I may be missing 
> something there (very likely)
>
>
> On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>>
>> I had a minor Eureka moment --- but it came to fraught (partially).
>>
>> I has a typo in the 'cas.properties' file: 
>> cas.serviceRegistry.json.location:file:/etc/cas/service
>>
>> i,e, 'service' instead of 'services' --- corrected now (validated that 
>> the json files are in '/etc/cas/services').
>>
>> But still no-go...any ideas will be matched by the maximum Karma I 
>> can provide.
>>
>> On Monday, May 14, 2018 at 4:16:39 PM UTC-7, Jann Malenkoff wrote:
>>>
>>> I'm on 5.2.4 --- I had earlier the 5.1 (i.e. 
>>> cas.serviceRegistry.config.location) 
>>> in 'cas.properties'--- now, updated to below (the 5.2.x version)
>>>
>>> cas.serviceRegistry.json.location:file:/etc/cas/service
>>> cas.serviceRegistry.initFromJson=true
>>>
>>> Still getting error below:
>>>
>>> 2018-05-14 16:11:41,016 WARN 
>>> [org.apereo.cas.services.web.ServiceThemeResolver] - >> is found to match 
>>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@3f670479[id=
>>> http://localhost:8080/cas-management/manage.html,originalUrl=http://locahost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>>  
>>> or service access is disallowed. Using default theme [cas-theme-default]>
>>>
>>> Json file:
>>>
>>> {
>>>   "@class" :"org.apereo.cas.services.RegexRegisteredService",
>>>   "serviceId" : "^(http)://.*",
>>>   "name" :  "HTTP wildcard",
>>>   "id" :20170905111650,
>>>   "evaluationOrder" :   9
>>> }
>>>
>>> Have I missed anything else? Could there be something else in the logs 
>>> that can give a clue (I have been hunting but may be missing it)?
>>>
>>> On Monday, May 14, 2018 at 3:47:36 PM UTC-7, Manfredo Hopp wrote:


 where are these pointing to:

 cas.serviceRegistry.json.location for 5.2.x 
 or 
 cas.serviceRegistry.config.location for 5.1.x

 2018-05-14 19:41 GMT-03:00 Jann Malenkoff :

> FYI --- the following appears in 'catalina.out' when attempting to 
> access 'http://localhost:8080/cas-management/manage.html,'.
>
> 2018-05-14 15:39:09,152 WARN 
> [org.apereo.cas.services.web.ServiceThemeResolver] -  service 
> is found to match 
> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=
> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>  
> or service access is disallowed. Using default theme [cas-theme-default]>
>
>
> On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
>>
>> Hi Richard:
>>
>> I have the following in 'cas.properties':
>>
>> cas.serviceRegistry.initFromJson=true
>>
>> Is that correct to enable the first read from JSON? I have been 
>> staring at the screen for so long and begining to doubt myself w.r.t 
>> true/false flags.
>>
>> On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:
>>>
>>> Do you have initialization on from JSON? Not sure if it will use 
>>> your file or just the defaults. Either way, it should get you into the 
>>> manager. Then you configure the manager service, and turn that property 
>>> off.
>>>
>>> # Auto-initialize the registry from default JSON service definitions
>>> # cas.serviceRegistry.initFromJson=false
>>>
>>>
>>>
>>> On 05/14/2018 05:13 PM, Jann Malenkoff wrote:
>>>
>>> Hi All:
>>>
>>> I'm trying to get the '
>>> http://localhost:8080/cas-management/manage.html' loaded up --- but 
>>> hitting the error message: 
>>> ' 
>>> Application Not Authorized to Use CAS 
>>>
>>> The services registry of CAS is empty and has no service 
>>> definitions. Applications that wish to authenticate with CAS must 
>>> explicitly be defined in the services registry.'
>>>
>>>
>>> I am hoping to have a JPA service registry --- and have configured 
>>> the dependencies below in the 'cas-overlay-template' 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Jann Malenkoff]

Attached is my 'cas.properties' file ---  in case I may be missing 
something there (very likely)


On Monday, May 14, 2018 at 5:09:12 PM UTC-7, Jann Malenkoff wrote:
>
> I had a minor Eureka moment --- but it came to fraught (partially).
>
> I has a typo in the 'cas.properties' file: 
> cas.serviceRegistry.json.location:file:/etc/cas/service
>
> i,e, 'service' instead of 'services' --- corrected now (validated that the 
> json files are in '/etc/cas/services').
>
> But still no-go...any ideas will be matched by the maximum Karma I can 
> provide.
>
> On Monday, May 14, 2018 at 4:16:39 PM UTC-7, Jann Malenkoff wrote:
>>
>> I'm on 5.2.4 --- I had earlier the 5.1 (i.e. 
>> cas.serviceRegistry.config.location) 
>> in 'cas.properties'--- now, updated to below (the 5.2.x version)
>>
>> cas.serviceRegistry.json.location:file:/etc/cas/service
>> cas.serviceRegistry.initFromJson=true
>>
>> Still getting error below:
>>
>> 2018-05-14 16:11:41,016 WARN 
>> [org.apereo.cas.services.web.ServiceThemeResolver] - > is found to match 
>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@3f670479[id=
>> http://localhost:8080/cas-management/manage.html,originalUrl=http://locahost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>  
>> or service access is disallowed. Using default theme [cas-theme-default]>
>>
>> Json file:
>>
>> {
>>   "@class" :"org.apereo.cas.services.RegexRegisteredService",
>>   "serviceId" : "^(http)://.*",
>>   "name" :  "HTTP wildcard",
>>   "id" :20170905111650,
>>   "evaluationOrder" :   9
>> }
>>
>> Have I missed anything else? Could there be something else in the logs 
>> that can give a clue (I have been hunting but may be missing it)?
>>
>> On Monday, May 14, 2018 at 3:47:36 PM UTC-7, Manfredo Hopp wrote:
>>>
>>>
>>> where are these pointing to:
>>>
>>> cas.serviceRegistry.json.location for 5.2.x 
>>> or 
>>> cas.serviceRegistry.config.location for 5.1.x
>>>
>>> 2018-05-14 19:41 GMT-03:00 Jann Malenkoff :
>>>
 FYI --- the following appears in 'catalina.out' when attempting to 
 access 'http://localhost:8080/cas-management/manage.html,'.

 2018-05-14 15:39:09,152 WARN 
 [org.apereo.cas.services.web.ServiceThemeResolver] - >>> service 
 is found to match 
 [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=
 http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
  
 or service access is disallowed. Using default theme [cas-theme-default]>


 On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
>
> Hi Richard:
>
> I have the following in 'cas.properties':
>
> cas.serviceRegistry.initFromJson=true
>
> Is that correct to enable the first read from JSON? I have been 
> staring at the screen for so long and begining to doubt myself w.r.t 
> true/false flags.
>
> On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:
>>
>> Do you have initialization on from JSON? Not sure if it will use your 
>> file or just the defaults. Either way, it should get you into the 
>> manager. 
>> Then you configure the manager service, and turn that property off.
>>
>> # Auto-initialize the registry from default JSON service definitions
>> # cas.serviceRegistry.initFromJson=false
>>
>>
>>
>> On 05/14/2018 05:13 PM, Jann Malenkoff wrote:
>>
>> Hi All:
>>
>> I'm trying to get the '
>> http://localhost:8080/cas-management/manage.html' loaded up --- but 
>> hitting the error message: 
>> ' 
>> Application Not Authorized to Use CAS 
>>
>> The services registry of CAS is empty and has no service definitions. 
>> Applications that wish to authenticate with CAS must explicitly be 
>> defined 
>> in the services registry.'
>>
>>
>> I am hoping to have a JPA service registry --- and have configured 
>> the dependencies below in the 'cas-overlay-template' pom.xml.
>>
>>
>> To enable the access to '
>> http://localhost:8080/cas-management/manage.html, I have added  the 
>> JASON entry as below --- but do not see it in the database table 
>> REGEXREGISTEREDSERVICE (I have cas.serviceRegistry.config.location:
>> file:/etc/cas/services in 'cas.properties).
>>
>>
>> What could I have missed (or more likely misunderstood)?
>>
>>
>> *JSON File in /etc/cas/services (copied -- slightly adjusted -- from 
>> an earlier post):*
>>
>> {
>>   /*
>>* Wildcard service definition that applies to any https or imaps 
>> url.
>>* Do not use this definition in a production environment.
>>*/
>>   "@class" :
>> 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Jann Malenkoff]

I had a minor Eureka moment --- but it came to fraught (partially).

I has a typo in the 'cas.properties' file: 
cas.serviceRegistry.json.location:file:/etc/cas/service

i,e, 'service' instead of 'services' --- corrected now (validated that the 
json files are in '/etc/cas/services').

But still no-go...any ideas will be matched by the maximum Karma I can 
provide.

On Monday, May 14, 2018 at 4:16:39 PM UTC-7, Jann Malenkoff wrote:
>
> I'm on 5.2.4 --- I had earlier the 5.1 (i.e. 
> cas.serviceRegistry.config.location) 
> in 'cas.properties'--- now, updated to below (the 5.2.x version)
>
> cas.serviceRegistry.json.location:file:/etc/cas/service
> cas.serviceRegistry.initFromJson=true
>
> Still getting error below:
>
> 2018-05-14 16:11:41,016 WARN 
> [org.apereo.cas.services.web.ServiceThemeResolver] -  is found to match 
> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@3f670479[id=
> http://localhost:8080/cas-management/manage.html,originalUrl=http://locahost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>  
> or service access is disallowed. Using default theme [cas-theme-default]>
>
> Json file:
>
> {
>   "@class" :"org.apereo.cas.services.RegexRegisteredService",
>   "serviceId" : "^(http)://.*",
>   "name" :  "HTTP wildcard",
>   "id" :20170905111650,
>   "evaluationOrder" :   9
> }
>
> Have I missed anything else? Could there be something else in the logs 
> that can give a clue (I have been hunting but may be missing it)?
>
> On Monday, May 14, 2018 at 3:47:36 PM UTC-7, Manfredo Hopp wrote:
>>
>>
>> where are these pointing to:
>>
>> cas.serviceRegistry.json.location for 5.2.x 
>> or 
>> cas.serviceRegistry.config.location for 5.1.x
>>
>> 2018-05-14 19:41 GMT-03:00 Jann Malenkoff :
>>
>>> FYI --- the following appears in 'catalina.out' when attempting to 
>>> access 'http://localhost:8080/cas-management/manage.html,'.
>>>
>>> 2018-05-14 15:39:09,152 WARN 
>>> [org.apereo.cas.services.web.ServiceThemeResolver] - >> is found to match 
>>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=
>>> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>>  
>>> or service access is disallowed. Using default theme [cas-theme-default]>
>>>
>>>
>>> On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:

 Hi Richard:

 I have the following in 'cas.properties':

 cas.serviceRegistry.initFromJson=true

 Is that correct to enable the first read from JSON? I have been staring 
 at the screen for so long and begining to doubt myself w.r.t true/false 
 flags.

 On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:
>
> Do you have initialization on from JSON? Not sure if it will use your 
> file or just the defaults. Either way, it should get you into the 
> manager. 
> Then you configure the manager service, and turn that property off.
>
> # Auto-initialize the registry from default JSON service definitions
> # cas.serviceRegistry.initFromJson=false
>
>
>
> On 05/14/2018 05:13 PM, Jann Malenkoff wrote:
>
> Hi All:
>
> I'm trying to get the '
> http://localhost:8080/cas-management/manage.html' loaded up --- but 
> hitting the error message: 
> ' 
> Application Not Authorized to Use CAS 
>
> The services registry of CAS is empty and has no service definitions. 
> Applications that wish to authenticate with CAS must explicitly be 
> defined 
> in the services registry.'
>
>
> I am hoping to have a JPA service registry --- and have configured the 
> dependencies below in the 'cas-overlay-template' pom.xml.
>
>
> To enable the access to '
> http://localhost:8080/cas-management/manage.html, I have added  the 
> JASON entry as below --- but do not see it in the database table 
> REGEXREGISTEREDSERVICE (I have cas.serviceRegistry.config.location:
> file:/etc/cas/services in 'cas.properties).
>
>
> What could I have missed (or more likely misunderstood)?
>
>
> *JSON File in /etc/cas/services (copied -- slightly adjusted -- from 
> an earlier post):*
>
> {
>   /*
>* Wildcard service definition that applies to any https or imaps 
> url.
>* Do not use this definition in a production environment.
>*/
>   "@class" :
> "org.apereo.cas.services.RegexRegisteredService",
>   "serviceId" : "^(http)://.*",
>   "name" :  "HTTP wildcard",
>   "id" :20180514,
>   "evaluationOrder" :   9
> }
>
>
> *pom.xml -- for cas-overlay-template*
>
> 
> 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Jann Malenkoff]

I'm on 5.2.4 --- I had earlier the 5.1 (i.e. 
cas.serviceRegistry.config.location) 
in 'cas.properties'--- now, updated to below (the 5.2.x version)

cas.serviceRegistry.json.location:file:/etc/cas/service
cas.serviceRegistry.initFromJson=true

Still getting error below:

2018-05-14 16:11:41,016 WARN 
[org.apereo.cas.services.web.ServiceThemeResolver] - http://localhost:8080/cas-management/manage.html,originalUrl=http://locahost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
 
or service access is disallowed. Using default theme [cas-theme-default]>

Json file:

{
  "@class" :"org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(http)://.*",
  "name" :  "HTTP wildcard",
  "id" :20170905111650,
  "evaluationOrder" :   9
}

Have I missed anything else? Could there be something else in the logs that 
can give a clue (I have been hunting but may be missing it)?

On Monday, May 14, 2018 at 3:47:36 PM UTC-7, Manfredo Hopp wrote:
>
>
> where are these pointing to:
>
> cas.serviceRegistry.json.location for 5.2.x 
> or 
> cas.serviceRegistry.config.location for 5.1.x
>
> 2018-05-14 19:41 GMT-03:00 Jann Malenkoff  >:
>
>> FYI --- the following appears in 'catalina.out' when attempting to access 
>> 'http://localhost:8080/cas-management/manage.html,'.
>>
>> 2018-05-14 15:39:09,152 WARN 
>> [org.apereo.cas.services.web.ServiceThemeResolver] - > is found to match 
>> [org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=
>> http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
>>  
>> or service access is disallowed. Using default theme [cas-theme-default]>
>>
>>
>> On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
>>>
>>> Hi Richard:
>>>
>>> I have the following in 'cas.properties':
>>>
>>> cas.serviceRegistry.initFromJson=true
>>>
>>> Is that correct to enable the first read from JSON? I have been staring 
>>> at the screen for so long and begining to doubt myself w.r.t true/false 
>>> flags.
>>>
>>> On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:

 Do you have initialization on from JSON? Not sure if it will use your 
 file or just the defaults. Either way, it should get you into the manager. 
 Then you configure the manager service, and turn that property off.

 # Auto-initialize the registry from default JSON service definitions
 # cas.serviceRegistry.initFromJson=false



 On 05/14/2018 05:13 PM, Jann Malenkoff wrote:

 Hi All:

 I'm trying to get the 'http://localhost:8080/cas-management/manage.html' 
 loaded up --- but hitting the error message: 
 ' 
 Application Not Authorized to Use CAS 

 The services registry of CAS is empty and has no service definitions. 
 Applications that wish to authenticate with CAS must explicitly be defined 
 in the services registry.'


 I am hoping to have a JPA service registry --- and have configured the 
 dependencies below in the 'cas-overlay-template' pom.xml.


 To enable the access to '
 http://localhost:8080/cas-management/manage.html, I have added  the 
 JASON entry as below --- but do not see it in the database table 
 REGEXREGISTEREDSERVICE (I have cas.serviceRegistry.config.location:
 file:/etc/cas/services in 'cas.properties).


 What could I have missed (or more likely misunderstood)?


 *JSON File in /etc/cas/services (copied -- slightly adjusted -- from an 
 earlier post):*

 {
   /*
* Wildcard service definition that applies to any https or imaps url.
* Do not use this definition in a production environment.
*/
   "@class" :
 "org.apereo.cas.services.RegexRegisteredService",
   "serviceId" : "^(http)://.*",
   "name" :  "HTTP wildcard",
   "id" :20180514,
   "evaluationOrder" :   9
 }


 *pom.xml -- for cas-overlay-template*

 
 
 org.apereo.cas
 
 cas-server-webapp${app.server}
 ${cas.version}
 war
 runtime
 
 
 org.apereo.cas
 
 cas-server-support-json-service-registry
 ${cas.version}
 
 
 org.apereo.cas
 cas-server-support-ldap
 ${cas.version}
 
 
 org.apereo.cas
 
 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Man H]

where are these pointing to:

cas.serviceRegistry.json.location for 5.2.x
or
cas.serviceRegistry.config.location for 5.1.x

2018-05-14 19:41 GMT-03:00 Jann Malenkoff :

> FYI --- the following appears in 'catalina.out' when attempting to access '
> http://localhost:8080/cas-management/manage.html,'.
>
> 2018-05-14 15:39:09,152 WARN 
> [org.apereo.cas.services.web.ServiceThemeResolver]
> -  authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=
> http://localhost:8080/cas-management/manage.html,originalUrl=http:/
> /localhost:8080/cas-management/manage.html,artifactId=,principal=<
> null>,loggedOutAlready=false,format=XML]] or service access is
> disallowed. Using default theme [cas-theme-default]>
>
>
> On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
>>
>> Hi Richard:
>>
>> I have the following in 'cas.properties':
>>
>> cas.serviceRegistry.initFromJson=true
>>
>> Is that correct to enable the first read from JSON? I have been staring
>> at the screen for so long and begining to doubt myself w.r.t true/false
>> flags.
>>
>> On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:
>>>
>>> Do you have initialization on from JSON? Not sure if it will use your
>>> file or just the defaults. Either way, it should get you into the manager.
>>> Then you configure the manager service, and turn that property off.
>>>
>>> # Auto-initialize the registry from default JSON service definitions
>>> # cas.serviceRegistry.initFromJson=false
>>>
>>>
>>>
>>> On 05/14/2018 05:13 PM, Jann Malenkoff wrote:
>>>
>>> Hi All:
>>>
>>> I'm trying to get the 'http://localhost:8080/cas-management/manage.html'
>>> loaded up --- but hitting the error message:
>>> '
>>> Application Not Authorized to Use CAS
>>>
>>> The services registry of CAS is empty and has no service definitions.
>>> Applications that wish to authenticate with CAS must explicitly be defined
>>> in the services registry.'
>>>
>>>
>>> I am hoping to have a JPA service registry --- and have configured the
>>> dependencies below in the 'cas-overlay-template' pom.xml.
>>>
>>>
>>> To enable the access to 'http://localhost:8080/cas-man
>>> agement/manage.html, I have added  the JASON entry as below --- but do
>>> not see it in the database table REGEXREGISTEREDSERVICE (I have
>>> cas.serviceRegistry.config.location:file:/etc/cas/services in
>>> 'cas.properties).
>>>
>>>
>>> What could I have missed (or more likely misunderstood)?
>>>
>>>
>>> *JSON File in /etc/cas/services (copied -- slightly adjusted -- from an
>>> earlier post):*
>>>
>>> {
>>>   /*
>>>* Wildcard service definition that applies to any https or imaps url.
>>>* Do not use this definition in a production environment.
>>>*/
>>>   "@class" :"org.apereo.cas.services.Regex
>>> RegisteredService",
>>>   "serviceId" : "^(http)://.*",
>>>   "name" :  "HTTP wildcard",
>>>   "id" :20180514,
>>>   "evaluationOrder" :   9
>>> }
>>>
>>>
>>> *pom.xml -- for cas-overlay-template*
>>>
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-webapp$
>>> {app.server}
>>> ${cas.version}
>>> war
>>> runtime
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support
>>> -json-service-registry
>>> ${cas.version}
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support-ldap
>>> ${cas.version}
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support
>>> -jpa-service-registry
>>> ${cas.version}
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support
>>> -jpa-ticket-registry
>>> ${cas.version}
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support
>>> -jdbc-drivers
>>> ${cas.version}
>>> 
>>> 
>>> com.oracle
>>> ojdbc7.jar
>>> 12.1.0.1
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support-saml
>>> ${cas.version}
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support-duo
>>> ${cas.version}
>>> 
>>> 
>>> org.apereo.cas
>>> cas-server-support
>>> -events-jpa
>>> ${cas.version}
>>> 
>>> 
>>> --
>>> - Website: https://apereo.github.io/cas
>>> - Gitter Chatroom: https://gitter.im/apereo/cas
>>> - 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Richard Frovarp]

Yes, you would want to flip that to true. There should be something in 
the logs. I don't remember which component actually does the work to do 
the initial import, if it is the server or the manager. I do seem to 
recall one of them logging something about importing it.


On 05/14/2018 05:41 PM, Jann Malenkoff wrote:
FYI --- the following appears in 'catalina.out' when attempting to 
access 'http://localhost:8080/cas-management/manage.html,'.


2018-05-14 15:39:09,152 WARN 
[org.apereo.cas.services.web.ServiceThemeResolver] - service is found to match 
[org.apereo.cas.authentication.principal.SimpleWebApplicationServiceImpl@13eed7a6[id=http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]] 
or service access is disallowed. Using default theme [cas-theme-default]>


On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:

Hi Richard:

I have the following in 'cas.properties':

cas.serviceRegistry.initFromJson=true

Is that correct to enable the first read from JSON? I have been
staring at the screen for so long and begining to doubt myself
w.r.t true/false flags.

On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:

Do you have initialization on from JSON? Not sure if it will
use your file or just the defaults. Either way, it should get
you into the manager. Then you configure the manager service,
and turn that property off.

# Auto-initialize the registry from default JSON service
definitions # cas.serviceRegistry.initFromJson=false



On 05/14/2018 05:13 PM, Jann Malenkoff wrote:

Hi All:

I'm trying to get the
'http://localhost:8080/cas-management/manage.html
' loaded up
--- but hitting the error message:
'
Application Not Authorized to Use CAS

The services registry of CAS is empty and has no service
definitions. Applications that wish to authenticate with CAS
must explicitly be defined in the services registry.'


I am hoping to have a JPA service registry --- and have
configured the dependencies below in the
'cas-overlay-template' pom.xml.


To enable the access to
'http://localhost:8080/cas-management/manage.html
, I have
added  the JASON entry as below --- but do not see it in the
database table REGEXREGISTEREDSERVICE (I have
cas.serviceRegistry.config.location: file:/etc/cas/services
in 'cas.properties).


What could I have missed (or more likely misunderstood)?


*JSON File in /etc/cas/services (copied -- slightly adjusted
-- from an earlier post):*

{
  /*
   * Wildcard service definition that applies to any https or
imaps url.
   * Do not use this definition in a production environment.
   */
  "@class" : "org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(http)://.*",
  "name" :  "HTTP wildcard",
  "id" :    20180514,
  "evaluationOrder" :   9
}



*pom.xml -- for cas-overlay-template*


    
org.apereo.cas
cas-server-webapp${app.server}
${cas.version}
    war
runtime
    
    
org.apereo.cas
cas-server-support-json-service-registry
${cas.version}
    
    
org.apereo.cas
   
cas-server-support-ldap
${cas.version}
    
    
org.apereo.cas
cas-server-support-jpa-service-registry
${cas.version}
    
    
org.apereo.cas
cas-server-support-jpa-ticket-registry
${cas.version}
    
    
org.apereo.cas
   
cas-server-support-jdbc-drivers
${cas.version}
    
    
com.oracle
ojdbc7.jar
12.1.0.1
    
    
org.apereo.cas
   
cas-server-support-saml
${cas.version}
    
    
org.apereo.cas
   
cas-server-support-duo
${cas.version}
    
    
org.apereo.cas
   
cas-server-support-events-jpa
${cas.version}
    

-- 
- Website: 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Jann Malenkoff]

FYI --- the following appears in 'catalina.out' when attempting to access 
'http://localhost:8080/cas-management/manage.html,'.

2018-05-14 15:39:09,152 WARN 
[org.apereo.cas.services.web.ServiceThemeResolver] - http://localhost:8080/cas-management/manage.html,originalUrl=http://localhost:8080/cas-management/manage.html,artifactId=,principal=,loggedOutAlready=false,format=XML]]
 
or service access is disallowed. Using default theme [cas-theme-default]>

On Monday, May 14, 2018 at 3:37:31 PM UTC-7, Jann Malenkoff wrote:
>
> Hi Richard:
>
> I have the following in 'cas.properties':
>
> cas.serviceRegistry.initFromJson=true
>
> Is that correct to enable the first read from JSON? I have been staring at 
> the screen for so long and begining to doubt myself w.r.t true/false flags.
>
> On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:
>>
>> Do you have initialization on from JSON? Not sure if it will use your 
>> file or just the defaults. Either way, it should get you into the manager. 
>> Then you configure the manager service, and turn that property off.
>>
>> # Auto-initialize the registry from default JSON service definitions
>> # cas.serviceRegistry.initFromJson=false
>>
>>
>>
>> On 05/14/2018 05:13 PM, Jann Malenkoff wrote:
>>
>> Hi All:
>>
>> I'm trying to get the 'http://localhost:8080/cas-management/manage.html' 
>> loaded up --- but hitting the error message: 
>> ' 
>> Application Not Authorized to Use CAS 
>>
>> The services registry of CAS is empty and has no service definitions. 
>> Applications that wish to authenticate with CAS must explicitly be defined 
>> in the services registry.'
>>
>>
>> I am hoping to have a JPA service registry --- and have configured the 
>> dependencies below in the 'cas-overlay-template' pom.xml.
>>
>>
>> To enable the access to 'http://localhost:8080/cas-management/manage.html, 
>> I have added  the JASON entry as below --- but do not see it in the 
>> database table REGEXREGISTEREDSERVICE (I have 
>> cas.serviceRegistry.config.location:file:/etc/cas/services in 
>> 'cas.properties).
>>
>>
>> What could I have missed (or more likely misunderstood)?
>>
>>
>> *JSON File in /etc/cas/services (copied -- slightly adjusted -- from an 
>> earlier post):*
>>
>> {
>>   /*
>>* Wildcard service definition that applies to any https or imaps url.
>>* Do not use this definition in a production environment.
>>*/
>>   "@class" :"org.apereo.cas.services.RegexRegisteredService",
>>   "serviceId" : "^(http)://.*",
>>   "name" :  "HTTP wildcard",
>>   "id" :20180514,
>>   "evaluationOrder" :   9
>> }
>>
>>
>> *pom.xml -- for cas-overlay-template*
>>
>> 
>> 
>> org.apereo.cas
>> 
>> cas-server-webapp${app.server}
>> ${cas.version}
>> war
>> runtime
>> 
>> 
>> org.apereo.cas
>> 
>> cas-server-support-json-service-registry
>> ${cas.version}
>> 
>> 
>> org.apereo.cas
>> cas-server-support-ldap
>> ${cas.version}
>> 
>> 
>> org.apereo.cas
>> 
>> cas-server-support-jpa-service-registry
>> ${cas.version}
>> 
>> 
>> org.apereo.cas
>> 
>> cas-server-support-jpa-ticket-registry
>> ${cas.version}
>> 
>> 
>> org.apereo.cas
>> 
>> cas-server-support-jdbc-drivers
>> ${cas.version}
>> 
>> 
>> com.oracle
>> ojdbc7.jar
>> 12.1.0.1
>> 
>> 
>> org.apereo.cas
>> cas-server-support-saml
>> ${cas.version}
>> 
>> 
>> org.apereo.cas
>> cas-server-support-duo
>> ${cas.version}
>> 
>> 
>> org.apereo.cas
>> cas-server-support-events-jpa
>> ${cas.version}
>> 
>> 
>> -- 
>> - 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 
>> 

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Jann Malenkoff]

Hi Richard:

I have the following in 'cas.properties':

cas.serviceRegistry.initFromJson=true

Is that correct to enable the first read from JSON? I have been staring at 
the screen for so long and begining to doubt myself w.r.t true/false flags.

On Monday, May 14, 2018 at 3:30:38 PM UTC-7, richard.frovarp wrote:
>
> Do you have initialization on from JSON? Not sure if it will use your file 
> or just the defaults. Either way, it should get you into the manager. Then 
> you configure the manager service, and turn that property off.
>
> # Auto-initialize the registry from default JSON service definitions
> # cas.serviceRegistry.initFromJson=false
>
>
>
> On 05/14/2018 05:13 PM, Jann Malenkoff wrote:
>
> Hi All:
>
> I'm trying to get the 'http://localhost:8080/cas-management/manage.html' 
> loaded up --- but hitting the error message: 
> ' 
> Application Not Authorized to Use CAS 
>
> The services registry of CAS is empty and has no service definitions. 
> Applications that wish to authenticate with CAS must explicitly be defined 
> in the services registry.'
>
>
> I am hoping to have a JPA service registry --- and have configured the 
> dependencies below in the 'cas-overlay-template' pom.xml.
>
>
> To enable the access to 'http://localhost:8080/cas-management/manage.html, 
> I have added  the JASON entry as below --- but do not see it in the 
> database table REGEXREGISTEREDSERVICE (I have 
> cas.serviceRegistry.config.location:file:/etc/cas/services in 
> 'cas.properties).
>
>
> What could I have missed (or more likely misunderstood)?
>
>
> *JSON File in /etc/cas/services (copied -- slightly adjusted -- from an 
> earlier post):*
>
> {
>   /*
>* Wildcard service definition that applies to any https or imaps url.
>* Do not use this definition in a production environment.
>*/
>   "@class" :"org.apereo.cas.services.RegexRegisteredService",
>   "serviceId" : "^(http)://.*",
>   "name" :  "HTTP wildcard",
>   "id" :20180514,
>   "evaluationOrder" :   9
> }
>
>
> *pom.xml -- for cas-overlay-template*
>
> 
> 
> org.apereo.cas
> cas-server-webapp${app.server}
> ${cas.version}
> war
> runtime
> 
> 
> org.apereo.cas
> 
> cas-server-support-json-service-registry
> ${cas.version}
> 
> 
> org.apereo.cas
> cas-server-support-ldap
> ${cas.version}
> 
> 
> org.apereo.cas
> 
> cas-server-support-jpa-service-registry
> ${cas.version}
> 
> 
> org.apereo.cas
> 
> cas-server-support-jpa-ticket-registry
> ${cas.version}
> 
> 
> org.apereo.cas
> 
> cas-server-support-jdbc-drivers
> ${cas.version}
> 
> 
> com.oracle
> ojdbc7.jar
> 12.1.0.1
> 
> 
> org.apereo.cas
> cas-server-support-saml
> ${cas.version}
> 
> 
> org.apereo.cas
> cas-server-support-duo
> ${cas.version}
> 
> 
> org.apereo.cas
> cas-server-support-events-jpa
> ${cas.version}
> 
> 
> -- 
> - 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/daad2fc6-3a69-4404-9a91-379cfd3ee24e%40apereo.org
>  
> 
> .
>
>
>

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

Re: [cas-user] Service Registry -- Getting the 1st Application Entered

[Richard Frovarp]

Do you have initialization on from JSON? Not sure if it will use your 
file or just the defaults. Either way, it should get you into the 
manager. Then you configure the manager service, and turn that property off.


# Auto-initialize the registry from default JSON service definitions # 
cas.serviceRegistry.initFromJson=false




On 05/14/2018 05:13 PM, Jann Malenkoff wrote:

Hi All:

I'm trying to get the 
'http://localhost:8080/cas-management/manage.html' loaded up --- but 
hitting the error message:

'
Application Not Authorized to Use CAS

The services registry of CAS is empty and has no service definitions. 
Applications that wish to authenticate with CAS must explicitly be 
defined in the services registry.'



I am hoping to have a JPA service registry --- and have configured the 
dependencies below in the 'cas-overlay-template' pom.xml.



To enable the access to 
'http://localhost:8080/cas-management/manage.html, I have added  the 
JASON entry as below --- but do not see it in the database table 
REGEXREGISTEREDSERVICE (I have cas.serviceRegistry.config.location: 
file:/etc/cas/services in 'cas.properties).



What could I have missed (or more likely misunderstood)?


*JSON File in /etc/cas/services (copied -- slightly adjusted -- from 
an earlier post):*


{
  /*
   * Wildcard service definition that applies to any https or imaps url.
   * Do not use this definition in a production environment.
   */
  "@class" : "org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(http)://.*",
  "name" :  "HTTP wildcard",
  "id" :    20180514,
  "evaluationOrder" :   9
}



*pom.xml -- for cas-overlay-template*


    
org.apereo.cas
cas-server-webapp${app.server}
${cas.version}
    war
    runtime
    
    
org.apereo.cas
cas-server-support-json-service-registry
${cas.version}
    
    
org.apereo.cas
cas-server-support-ldap
${cas.version}
    
    
org.apereo.cas
cas-server-support-jpa-service-registry
${cas.version}
    
    
org.apereo.cas
cas-server-support-jpa-ticket-registry
${cas.version}
    
    
org.apereo.cas
cas-server-support-jdbc-drivers
${cas.version}
    
    
    com.oracle
ojdbc7.jar
    12.1.0.1
    
    
org.apereo.cas
cas-server-support-saml
${cas.version}
    
    
org.apereo.cas
cas-server-support-duo
${cas.version}
    
    
org.apereo.cas
cas-server-support-events-jpa
${cas.version}
    

--
- 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/daad2fc6-3a69-4404-9a91-379cfd3ee24e%40apereo.org 
.



--
- 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/a400af15-af98-97b5-5020-f12b16dd905d%40ndsu.edu.

[cas-user] Service Registry -- Getting the 1st Application Entered

[Jann Malenkoff]

Hi All:

I'm trying to get the 'http://localhost:8080/cas-management/manage.html' 
loaded up --- but hitting the error message: 
'
Application Not Authorized to Use CAS 

The services registry of CAS is empty and has no service definitions. 
Applications that wish to authenticate with CAS must explicitly be defined 
in the services registry.'


I am hoping to have a JPA service registry --- and have configured the 
dependencies below in the 'cas-overlay-template' pom.xml.


To enable the access to 'http://localhost:8080/cas-management/manage.html, 
I have added  the JASON entry as below --- but do not see it in the 
database table REGEXREGISTEREDSERVICE (I have 
cas.serviceRegistry.config.location:file:/etc/cas/services in 
'cas.properties).


What could I have missed (or more likely misunderstood)?


*JSON File in /etc/cas/services (copied -- slightly adjusted -- from an 
earlier post):*

{
  /*
   * Wildcard service definition that applies to any https or imaps url.
   * Do not use this definition in a production environment.
   */
  "@class" :"org.apereo.cas.services.RegexRegisteredService",
  "serviceId" : "^(http)://.*",
  "name" :  "HTTP wildcard",
  "id" :20180514,
  "evaluationOrder" :   9
}


*pom.xml -- for cas-overlay-template*



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


org.apereo.cas

cas-server-support-json-service-registry
${cas.version}


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


org.apereo.cas

cas-server-support-jpa-service-registry
${cas.version}


org.apereo.cas

cas-server-support-jpa-ticket-registry
${cas.version}


org.apereo.cas
cas-server-support-jdbc-drivers
${cas.version}


com.oracle
ojdbc7.jar
12.1.0.1


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


org.apereo.cas
cas-server-support-duo
${cas.version}


org.apereo.cas
cas-server-support-events-jpa
${cas.version}



-- 
- 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/daad2fc6-3a69-4404-9a91-379cfd3ee24e%40apereo.org.