Developers,
1) Wrote this blog post about blunt instrument response to being locked
out of services management application when using JPA services registry.
http://www.unicon.net/blog/apetro/disable_cas_services_registry_authentication
2) It seems like the services registry could always consider the
services management application authorized to use CAS for
authentication. The identifier for this application is available in
cas.properties. Would it make things better or worse for the services
registry (Or CASImpl in front of it) to be aware of and exceptionally
treat as permitted to use CAS regardless of registration the services
management application URL as configured in properties?
It's annoying complexity to add, but it also seems to invite Catch-22s
to have the mechanism for administrative registration of services itself
have to be registered via that administrative mechanism.
Andrew
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
