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
Workflow | Original: JAC Suggestion Workflow [ 3388492 ] | New: JAC Suggestion Workflow 3 [ 3630511 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1391271 ] | New: JAC Suggestion Workflow [ 3388492 ] |
Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] | |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 273331 ] | New: Simplified Crowd Development Workflow v2 [ 1391271 ] |
Workflow | Original: Feature Request Workflow [ 173801 ] | New: Crowd Development Workflow v2 [ 273331 ] |
Fix Version/s | New: 2.1 [ 14496 ] | |
Resolution | New: Obsolete [ 11 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: jira [ 129300 ] | New: Feature Request Workflow [ 173801 ] |