A newly created app shows up for some Contributor users, and not others, even though these users are all in the same group. I've double checked the rights in CAC, and everyone in this group has Edit rights to all eList items.
Another newly created app does not show up for ANY Contributor user (that I've checked), even for the System Administrator. I'm having no problems with older, existing apps.
Any ideas where to check? Using Cognos 8.4.27.80 - Access Manager 7.3 as Authentication Provider.
Thanks!
Hey there,
This topic can be a pain to troubleshoot because of the many MANY ways you can accomplish security and the defaults that can be manipulated. The places I would look:
1. If you have Cognos namespace groups and roles defined with users from accman assigned rights to elists in the CAC make sure the package in cognos connection contains those objects.
Ex: If you have a Cognos namespace role called 'Americas' and this is the item assigned rights to an elist in the CAC, you should see 'Americas' in the package permissions with read, execute and traverse permissions.
2. If you have Accman userclasses (not users) assigned rights to elists, you will want to make sure that that shows up in the package permissions. Also confirm in Accman administration that the users have membership to that userclass.
3. If you have userclasses added to Cognos namespace groups or roles, you'll want to ensure that membership is setup properly in accman administration.
If all else fails, I would:
1. Create a new userclass in accman under Root User Class.
2. Create a new 'testuser' account and make it a member of the new userclass in step 1.
3. Add this userclass to your Planning Contributor Users role in the cognos namespace (you need to be, at minimum, a member of this Role to access Cognos Connection)
4. You can then assign the userclass to a right within an application.
5. At this point, log into cognos connection with the new user and confirm if you can see the application.
6. If you can see it, then back in accman administration remove the membership of the user to the userclass.
7. Log out of cognos connection and log back in. You shouldn't see the application any further until you register its membership again.
If this works then this confirms that security is working OK and you'll have to step through your configurations to see if you can pinpoint the problem.
Hope this helps.
Aha - it was a problem in the namespace groups. Thanks for pointing me in the right direction. :D
No worries, I'm glad you were able to figure it out. :)
Cheers.