Users in multiple namespaces

[Steve]

Hi Folks -

Currently we have 2 Active Directories configured , one for Internal users and one for external and none of them have SSO enabled so we provide credentials for logging in. If we use Azure AD instead of AD for External users and implement SSO with it, we can still have the other AD for Internal users work without SSO? Is that a correct understanding?

Also, what will happen to the reports in 'My Folders' when we discontinue the current namespace for External users and use the name namespace for Azure AD? Also, currently there are two URLs to access Cognos, one for Internal and one for External but I see only one in Cognos Configuration ! The internal one ! Is there a way to associate a namespace with the URL because it asks me to log on to the internal namespace. When I use the URL for the external users then it asks me to log on to the namespace meant for external users. I wonder where is the association of the URL with the namespace for security provider ! Any ideas?

Thanks for your help !

[JCarter]

Hi Steve,
It's been awhile since I worked with our instance that had more than one namespace (maybe back in 10.1?), but at that time, it was configured so that one of the namespaces had SSO configured and the 2nd namespace required user/pass to logon. I wouldn't expect that to have changed.

When you migrate over to an alternate namespace, all users will have brand new blank My Content folders, unless you jump through some hoops to either retain CAMIDs or migrate content to each user's new CAMID.

I'm less sure about the urls, but my thought would be that Cognos is configured with the internal URL, but your web server (IIS? Apache?) is doing something to help Cognos know which namespace to use, maybe passing a client certificate. This is just a guess though, as we don't have external access to Cognos where I am.

[Eric.Pleiss]

You'll need to map the old CAMIDs to the CAMIDs in the new namespace provider if you want to maintain the My Folder content. 

This can be a tedious and long process, ripe for error without some sort of automation. 

BSP Software has a Security Migration tool set up to handle this, as well as any other security migration related things (group and role membership, security policies, etc).

https://www.bspsoftware.com/products/metamanager/smss/

If you're interested in learning more, let me know.