It's all about the answers!

Ask a question

Get communities specific to user


Kiran Kumar R (77810) | asked Sep 17 '12, 9:57 a.m.
edited Sep 17 '12, 10:25 a.m.

Hi,

  Im working on creating a C#.Net application which integrates RAM with TFS using REST API. I use the REST  urls to get specific details. Such as, this url "http://server:port/ram/internal/communities" returns the list of the communities present in RAM. My requirement is to know the url used to get the list of communities according to specific user. In RAM, specific user has access to specific communities. I want to get those specific community details for the user who is authenticated. 

Regards,

Kiran


EDIT: Removed OSLC. We are using REST APIs.



Comments
Eric Bordeau commented Sep 17 '12, 10:22 a.m.
JAZZ DEVELOPER

Note that http://server:port/ram/internal/communities is not part of the OSLC Asset specification. It's an internal URL that should not be used except by RAM itself.

Accepted answer


permanent link
Kangkan Goswami (1571521) | answered Nov 30 '12, 5:07 a.m.
Please use the following query to get the Communities for which the user is having permission:

http://server:port/ram/oslc/servicesCatalog


Kiran Kumar R selected this answer as the correct answer

One other answer



permanent link
Peter Walker (168136) | answered Sep 18 '12, 12:28 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
With regards to your question about a REST call to determine if a specific user has access to specific communities, the answer is no. This is an administration function and even the RAM Java client API doesn't have that capability although I believe there is an enhancement request on jazz.net to be considered in the future.

As Eric commented earlier, the REST calls you are using are internal API calls and you may use them but they are not supported and may change in the future. Although we encourage REST calls through the OSLC specification... and is the direction we want our users to move in...  this is still underway and not yet complete. "Communities" is very RAM specific and thus only "internal" API is available that is used by RAM itself. Feel free to use at your own risk.

Your answer


Register or to post your answer.