The SecurityServerClient API could use some improvements:
Have a complete, symmetrical API across all the SOAPEntity types (Principal, Group, Role). This should include at least the following (examples for Principal only):
addPrincipal(SOAPPrincipal)
removePrincipal(SOAPPrincipal)
updatePrincipal(SOAPPrincipal)
Have the SecurityServerClient use Lists rather than Arrays when returning collections of SOAPEntities. Even if this is only outward-facing and handled as Arrays internally, that is fine. Failing that, a Util class would be nice for wrestling with arrays. See this thread for details.
- is related to
-
CWD-1309 REST API for Crowd
- Closed
[CWD-1151] Improve the SecurityServerClient API, possibly the SOAP API also
Further, because of backwards compatibility, it may be beneficial to create a new outward-facing Client API that talks to the SOAP API internally. This API could be tailored specifically for developer use.
class CrowdClient, containing everything in SSC and more, as described above.
class CrowdUser (to reflect the terminology switch from Principal to User)
class CrowdGroup
class CrowdRole
abstract class CrowdEntity
class CrowdDirectory (potentially for lower-level Crowd operations from the client someday)
Just as an aside, to a new developer (such as others in my organization), the terminology of the Client API is confusing; they don't know what a SecurityServerClient or a SOAPPrincipal is. A more name-friendly API could be beneficial.
The new Crowd REST API is cleaner, more comprehensive, and will replace the SOAP API for new development.