It's all about the answers!

Ask a question

RAM API for bind user group and create lifecycle


pan tianming (4765644) | asked Feb 21 '12, 3:33 a.m.
We have following steps need to do each time for config RAM community manually:
1) Using RAM admin user login and go to administration -> community

2) Create lifecycle for the enterprise community:
a. From the Roles tab, click Asset Producer.
b. Set the role permissions to:
Create assets
Download assets
Read asset details
Search assets
Subscribe to assets
c. Click OK.

3)
a. From the Users tab, click New User Group to create a new user group for the community.
b.Configure the group as follows:
Name, Description, Group roles
c. Click Create. The Bind a User Group to External Registry window opens.
Search for the LDAP group name that matches the community name. Then
click Bind.
Tip: If the Create link is not there, you will need to navigate back to the
Administration tab. Select Configuration from the Repository Administration menu on the right panel. Scroll to the Custom User Registry section and make sure the Use a Custom User Registry option is checked. Then start over from
step 8.
d.Click OK."

Could you help to confirm if above steps can be implemented by RAM API codes?
Thanks.

2 answers



permanent link
Rich Kulp (3.6k38) | answered Feb 22 '12, 9:53 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi,

Sorry, Admin API is not available.

Rich

permanent link
Rogério Ramos da Silva (33512827) | answered Feb 23 '12, 7:12 a.m.
Hi,

Sorry, Admin API is not available.

Rich


Hi Rich,

It's a great point to discuss about, like Pantian I've been suffering the same rework each time the new RAM's version/release is available.
Even importing a defined structure of an existent RAM server, this parts of the repository isn't imported and in my case is the harder piece of any upgrading or evaluation of version.
Is There some planning to expose this API or improve the Batch Update Tool to provide this?

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.