Author Topic: Custom Authentication Namespace  (Read 121 times)

Offline Wolverine

  • Full Member
  • ***
  • Join Date: Mar 2018
  • Posts: 13
  • Forum Citizenship: +0/-0
Custom Authentication Namespace
« on: 15 Mar 2019 04:06:31 pm »
Hello.  We are using V 11.0.12 on MS Server 2016, MS  SQL DB 2017, IIS 10.  The way our environment is setup we have to use a CJAP.  I dropped the .jar file in the location it is supposed to be in. When I go to the Cognos frontend I can see it in Cognos Administration/Security Tab, but it is greyed out (see attachment).  Any ideas on why it is greyed out or how to get it to be active?  Please help!!

Online bus_pass_man

  • Statesman
  • ******
  • Join Date: May 2008
  • Posts: 277
  • Forum Citizenship: +34/-0
Re: Custom Authentication Namespace
« Reply #1 on: 15 Mar 2019 04:16:08 pm »
Click on log on, which at the right near the top, and log in.


Offline Wolverine

  • Full Member
  • ***
  • Join Date: Mar 2018
  • Posts: 13
  • Forum Citizenship: +0/-0
Re: Custom Authentication Namespace
« Reply #2 on: 18 Mar 2019 10:00:41 am »
You make it sound too easy.... BUT....

This is a brand new install and there are no users except "Anonymous". We are trying to connect to the "Third Party Authentication" via Custom Java to add users to Cognos Namespace Groups. However, the third part does not allow "Anonymous" connections.

So the real question is; How do you get the external namespace active in the Administration Tab to allow Cognos to see the users?

This is the proverbial case of the "Chicken and the Egg"!

Offline Kiran P

  • Community Leader
  • *****
  • Join Date: Oct 2013
  • Posts: 124
  • Forum Citizenship: +2/-0
Re: Custom Authentication Namespace
« Reply #3 on: 20 Mar 2019 05:24:08 am »
I am not sure how your custom Java authentication is built but in our case the java module generates a cache containing information about users and their roles as defined in our web application. Then the CAP jar files load these users into cognos thus making them available to content store. So, when we go to custom namespace we already see users and there is no way to add users there.

In our case, we have AD and CAP authentication, so we login with CAP credentials first and then with AD again to impersonate sysadmin access and assign these custom namespace users to content - reports , dashboards, folders etc.

Thanks,
Kiran

Offline Wolverine

  • Full Member
  • ***
  • Join Date: Mar 2018
  • Posts: 13
  • Forum Citizenship: +0/-0
Re: Custom Authentication Namespace
« Reply #4 on: 22 Mar 2019 01:28:22 pm »
Thanks, this gives us some new ideas.

However, we do not have admin rights to the Authentication provider. It works like a 'black box' to us. We submit the Java request to the web service and Cognos gets a response.

 


       
Twittear