Cognos Analytics

Cognos Analytics

Connect, learn, and share with thousands of IBM Cognos Analytics users! 

 View Only

  • 1.  Multiple Namespace configured with default namespace

    Posted Tue April 16, 2024 05:28 PM

    Hi everyone

    I have multiple AD domains configured on Cognos 11.2.4

    I would like to set one of them as the default namespace which I expect the users form default namespace directly login to the system via SSO, while other users coming through other namespaces are asked to enter credentials when they click on the Cognos Analytics link.

    Is there a way to achieve this rather than adding namespace parameter at the end of gateway URL?

    Regards

    Sukru



    ------------------------------
    Sukru Haciyanli
    ------------------------------


  • 2.  RE: Multiple Namespace configured with default namespace

    Posted Wed April 17, 2024 09:04 AM

    The only thing that may work is to use tenancy and give each group its own access route.



    ------------------------------
    Carl Richardson
    ------------------------------



  • 3.  RE: Multiple Namespace configured with default namespace

    Posted Fri April 19, 2024 01:09 AM
    Edited by Sukru Haciyanli Fri April 19, 2024 01:12 AM

    Dear Carl

    Thank you very much for your answer.

    We took it into consideration. As far as the environment is not a cloud platform and both domains are belonging to the same multidomain tree, we thought there might be a simple solution. But up to now we have not found a workaround so we will give a try to tenancy.



    ------------------------------
    Sukru Haciyanli
    ------------------------------

    Original Message


  • 4.  RE: Multiple Namespace configured with default namespace

    Posted Thu April 18, 2024 04:30 AM

    Hi Sukru,

    You have everything you need in Configuring a gateway namespace page:

    https://www.ibm.com/docs/en/cognos-analytics/12.0.0?topic=namespaces-configuring-gateway-namespace

    Best regards,



    ------------------------------
    Patrick Neveu
    Collaboration Betters The World (CBTW)
    IBM Champion
    ------------------------------



  • 5.  RE: Multiple Namespace configured with default namespace

    Posted Thu April 18, 2024 08:45 AM

    AS usual someone at IBM does not understand the Question and point to a manual that does not answer the question.

    veteran IBM customer

    CR



    ------------------------------
    Carl Richardson
    ------------------------------

    Original Message


  • 6.  RE: Multiple Namespace configured with default namespace

    Posted Thu April 18, 2024 11:02 AM

    Sukru,

    I assume you will have at least 2 gateways, one with the configuration Gateway namespace defined using SSO (it would be used by internal users, I guess) and the other gateway would be used for the other namespace (maybe available for external users).

    Best regards,



    ------------------------------
    Patrick Neveu
    Collaboration Betters The World (CBTW)
    IBM Champion
    ------------------------------

    Original Message


  • 7.  RE: Multiple Namespace configured with default namespace

    Posted Fri April 19, 2024 01:32 AM

    Hi Patrick

    Thanks for your guidence. But the problem is environment belongs to one huge organization. Domain 1 is configured for IT department and domain 2 is configured for other business units. For the last couple of years everyone were using the namespace selection method in the login page when accessing the Cognos reports. All schedules, event triggers etc. were configured. Now business users are not comfortable with selecting the NS everytime. Adding a new gateway and changing the url will affect lots of things with the previously configured url's, portal integrations, distributions and so on.

    Thanks.



    ------------------------------
    Sukru Haciyanli
    ------------------------------

    Original Message


  • 8.  RE: Multiple Namespace configured with default namespace

    Posted Mon April 22, 2024 10:45 AM

    You may be able to address this with what is commonly referred to as a Trusted Sign-on Provider (TSP). This is a simpler version of a custom authentication provider that can be used to accomplish a number of simple tasks before redirecting to another name space. In this case you may be able to code it to determine if the user should be directed to the SSO name space or the other one based on something like name. This TSP then becomes the default name space for everyone.



    ------------------------------
    Robert Hofstetter
    ------------------------------



Related Content