Hi Everyone,
I have configured New Active directory in Cognos configuration. AD test completes successfully.
But when i try to login with a User, I'm getting 'This page cannot be displayed.It may be deleted or you may not have sufficient privileges to see it'.
i have attached screenshot of the same.
Can anyone help in addressing this issue?
Few users are facing this issue, so its urgent.
Thanks
Quote from: White light on 13 Aug 2020 11:38:02 AM
Hi Everyone,
I have configured New Active directory in Cognos configuration. AD test completes successfully.
But when i try to login with a User, I'm getting 'This page cannot be displayed.It may be deleted or you may not have sufficient privileges to see it'.
i have attached screenshot of the same.
Can anyone help in addressing this issue?
Few users are facing this issue, so its urgent.
Thanks
Hi,
What privileges are granted and to which groups/roles in the root of Team Content? I'm guessing the new users have no privileges?
MF.
Hi MF,
Thanks for the response.
Please guide me on where I can check these privileges for users. Is it in AD?
For anonymous access also same page is being displayed.
Thanks
Quote from: White light on 13 Aug 2020 01:27:53 PM
Hi MF,
Thanks for the response.
Please guide me on where I can check these privileges for users. Is it in AD?
For anonymous access also same page is being displayed.
Thanks
Hi,
No, it's not in AD, it's in the Cognos portal. Expand the Team Content pane by clicking on Team Content in the Nav Bar, and at the top of the pane is a Properties button. Go to the Permissions tab within the Properties pane, and you will see the which privileges are defined for which groups and roles. YOu can add in any missing groups or roles at this point and specify what permissions you want them to have.
I'd recommend you read up on the security model in the CA documentation, too.
https://www.ibm.com/support/knowledgecenter/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.ug_cra.doc/c_accesspermissions.html
Cheers!
MF.
Hi MF,
Our company is migrating User accounts from One domain to another.
So currently two AD's are working as authentication source(one for users in old domain and another for users in new domain)
My account has not yet been moved to New domain but some of the users account has been.
How can i provide permissions to the migrated users?
As of now, i am able to login only through users. So i don't have access to Public Folders
And also administration option under launch is not available.
Can you please help me out?
Thanks
Quote from: White light on 14 Aug 2020 08:35:36 AM
Hi MF,
Our company is migrating User accounts from One domain to another.
So currently two AD's are working as authentication source(one for users in old domain and another for users in new domain)
My account has not yet been moved to New domain but some of the users account has been.
How can i provide permissions to the migrated users?
As of now, i am able to login only through users. So i don't have access to Public Folders
And also administration option under launch is not available.
Can you please help me out?
Thanks
Hi,
The trick here is to log into both namespaces. Log in as usual to the namespace that gives you your Admin privileges, then without logging out, use the log on option to log in a second time to the other namespace. You will then have access to the users and groups from both namespaces, and the sum of your privileges from both.
Cheers!
MF.
Thanks MF!!! That worked. Neat trick.
But users are getting 'Access Denied' message on 'My folders' tab. I think it is due to CAMID changes as I added them to Cognos namespace from New namespace.
I have user's profile still available in old namespace as they are to be deleted a month after migration.
Can simply copying User's profile from Old namespace to New namespace address this issue?
Or are there any other approaches i can take to restore user's My Folders content and provide access to it?
Number of users are less, so i don't mind doing it manually if there is such option.
Thanks
WL
'Access Denied' was due to permissions issue. It is resolved after providing users with suitable access rights.
Thanks for the support MF.