Skip to end of metadata
Go to start of metadata

Used from UserAdminWebApp

Resource Method Expect Description
User(s)
"users/find/"+query GET Json  
"user/uid GET Json  
"user/uid PUT Json  
"user/uid DELETE Json  
"user/ POST Json  
Role
"user/"uid"/roles" GET Json  
"user/"uid"/roles" POST Json  
"user/"uid"/role/"+roleId DELETE Json  
"user/"uid"/role/"+roleId PUT Json  
Password
"password/" + apptokenid +"/reset/username/" + username POST Json  
Applications
"applications" GET Json  

Used from 3.party apps

Resource Method Expect Description
User(s)
"users/find/"+query GET XML  
"user/uid GET XML  
"user/uid PUT XML  
"user/uid DELETE XML  
"user/ POST XML  
Role
"user/"uid"/roles" GET XML  
"user/"uid"/roles" POST XML  
"user/"uid"/role/"+roleId DELETE XML  
"user/"uid"/role/"+roleId PUT XML  
Password
"password/" + apptokenid +"/reset/username/" + username POST XML  
Applications
"applications" GET XML  

....

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Dec 13, 2014

    Note that we might have use cases where we sometime need to limit the response to UserIdentity objects and not the full UserAggregate. Also for UserAggregate we might consider filtering on the application-level of the aggregate, so only a given or a set of defined applications are part of the outbound UserAggregate object