CAS Community, I am working on a changeset to allow the CAS LDAP Service Registry to persist changes back into LDAP as JSON blobs. While we now persist CAS service properties as individual LDAP attributes one by one, I have in mind that it would be easier if we converted the entire service definition into JSON and saved it as a whole into a single attribute. This is easier to manage and implement, as the configuration of attribute names and objectclasses would be simplified, but the disadvantage is that direct control over those individual attributes would be lost, if one were to manually change a service url in LDAP. Unless you were to use the management webapp to handle service changes, you'd be sort of forced to manually tweak the JSON blob inside that single attribute.
I am reaching out to see if the proposed approach of combining everything down to a single attribute value as JSON makes sense to those that use the LDAP service registry and whether said disadvantages would be an actual shortcoming in practice. I have yet to come across a CAS deployment that uses this particular registry type, but I understand there are others that have used an deployed it. Feedback is most welcome. Misagh -- 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
