Has the configuration changed for the JSON service registry with the
addition of the real-time reloading in the newer version cas-addons?
Here's what I have in deployerConfigContext.xml:
<bean id="serviceRegistryDao"
class="net.unicon.cas.addons.serviceregistry.JsonServiceRegistryDao"
init-method="load" >
<constructor-arg index="0"
value="${cas.serviceRegistry.servicesConfigFile}"/>
</bean>
cas.serviceRegistry.servicesConfigFile is a property in an external config
file. And here's the JSON file:
{
"services": [
{
"enabled": true,
"ignoreAttributes": false,
"theme": "impersonate",
"id": 1,
"extraAttributes": {
"createdDate": "2012-08-23"
},
"allowedToProxy": false,
"serviceId": "https://dev.it.usf.edu/**";,
"description": "Dev server",
"name": "DEV",
"ssoEnabled": true,
"anonymousAccess": false,
"evaluationOrder": 100,
"allowedAttributes": [
"USFeduUnumber"
]
}
]
}
This works fine with any version of cas-addons before 0.9.5, but when I try
any version that includes real-time file reloading, it isn't read at all
and CAS reverts to default behavior: release all attributes to everyone. I
get log messages from ReloadableServicesManagerSuppressionAspect, but the
loadServices method never runs at all. Is there something I need to change
in my config to get the reloading to work? Does the JSON file need to be
in the WEB-INF directory?
Thanks,
-Eric
--
Eric Pierce
Identity Management Architect
Information Technology
University of South Florida
(813) 974-8868 -- [email protected]
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
