If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Directory Namespace in IBM's cloud

Started by dougp, 24 Jun 2022 02:50:40 PM

Previous topic - Next topic

dougp

The docs I'm seeing to set up a directory namespace using Active Directory in Cognos Analytics (for example, https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=server-configuring-active-directory-namespace) says the first step is to "open IBM Cognos Configuration".  I'm pretty sure IBM won't give me access to run Cognos Configuration on the "IBM Cognos in the Cloud" service.  So, how would I set this up?

MFGF

Quote from: dougp on 24 Jun 2022 02:50:40 PM
The docs I'm seeing to set up a directory namespace using Active Directory in Cognos Analytics (for example, https://www.ibm.com/docs/en/cognos-analytics/11.2.0?topic=server-configuring-active-directory-namespace) says the first step is to "open IBM Cognos Configuration".  I'm pretty sure IBM won't give me access to run Cognos Configuration on the "IBM Cognos in the Cloud" service.  So, how would I set this up?

Hi Doug,

I'm assuming you're referring to the Cognos Analytics on Cloud Hosted service? When you sign up for this service, it is provisioned initially with a BI on Cloud LDAP authentication source. You receive a Welcome Letter and a VPN document, both of which need to be completed and sent back to IBM. In the Welcome Letter, you specify the details of what authentication source you want to use (you can continue to use the provided LDAP if you wish, or you can specify your own provider). When IBM's CloudOps team receives the completed Welcome Letter, they configure the authentication provider on your behalf, so you temporarily end up with two authentication namespaces. You are then required to transfer Cognos Administration rights from the LDAPAdmin user to a user from your namespace. Log in using that user, and test everything is ok. You can then request that the LDAP namespace be removed.

Cheers!

MF.
Meep!