It's all about the answers!

Ask a question

when iRAM gives 'You are authorized to view community error?


iRAM Administrator (3152146135) | asked Nov 30 '10, 3:43 p.m.
iRAM Sign-In users are getting "You are authorized to view the <<community>> . Request permission to the <<community>>." error message, after click the community name listed under the "Community" tab.

1. What are all can be the reasons for getting this error message after Click the community name listed under community tab ?

As per our investigation, this error message is NOT coming frequently, many times; this community page is opening successfully for the Sign-In Users. But this rare error message comes in the community, where the Sign-in users ROLE is having condition (Category or Asset type).

For an example, "IBM Green to Open Software G2O" , "IBM STG Client Facing" communities are giving this error message some times, In these community, the "Asset Consumer" Role is assigned to the "Sign-in" users, but community administrators added the category condition under "Role scopes" section of this Asset consumer role. This error message comes, when the user click this type of communities.

Kindly explain more about this behavior.

2 answers



permanent link
Sheehan Anderson (1.2k4) | answered Nov 30 '10, 4:04 p.m.
JAZZ DEVELOPER
This is a bug. If you constrain the scope of a role, users with that role will be unable to view the community home page.
It is being tracked at
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/25212

permanent link
iRAM Administrator (3152146135) | answered Dec 07 '10, 12:08 p.m.
This is a bug. If you constrain the scope of a role, users with that role will be unable to view the community home page.
It is being tracked at
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/25212





We have verified the issue in IHE environment where our test servers are hosted, and the issue does not occur there.

Our client too confirmed and raising the concern that this was not existing before and the iRAM application version is same on current production and test environment being talked here.

We have raised following PMR 33825-004 , (Issue #1217) to seek some work around.

The impact seen is huge for us and wish we have any date for a workaround.

Your answer


Register or to post your answer.