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

SSO implemented but not with URL

Started by Naven, 02 Jun 2009 01:47:52 AM

Previous topic - Next topic

Naven

Hi All,

       Few days ago I tried to implent Single Sign On and I was successful of doing that.When I tried it with http://server IP:9300/samples/setCookie.jsp(9300 - runs application server), it works but when tried it with actual URL it did'nt as it hits webserver(port 8000) first.

       I followed cognos recommended approach: (KB 1008286) - Cognos 8 SDK JSP sample demonstrates how to set up a cam_passport cookie.Its a jsp which I need to keep in cognos installation location\webapps\samples.

Here comes the problem:Our application server(webserver installed in the same server) runs on 9300.
And webserver runs on 8000 and the policy is any request should go through webserver only, I cant change that.But anyhow I need to run the JSP first(which can run only on 9300) so that SSO can be done.

I have tried to connect apache - tomcat connector with mod_jk which can redirect me form 8000 to 9300 but I failed to do that.I followed the link to apply mod_jk:

"http://www.johnturner.com/howto/winxp-howto.html"

I also tried the PDF suggested by Cognos(page 50):"managing_apache_webserver.pdf"

One more thing, our production is a distributed environmnet and we are using load balancer so virtula IP comes to the picture.Any how I am trying it in DEV which is not distributed.

Can anybody help me on this case.

Thanks in advance

Avik(on behalf of Naveen)

Kleber

That load lancer URL you have is not Cognos owned or supported, right?
I tried doing the same thing a few years ago but we started facing some other issues, for example when the user tried to open an interactively run report, the client computer would try to grab the report from the wrong cognos gateway computer because the load balancer tried to redirect the connection to the another server where cognos didn't have the report cached, among some other problems. I ended up elimating the load balancer and introduced a single point of failure unfortunately, but I would be interested in knowing if you're able to overcome this challenge with the SSO and knowing what kind of load balancer you have.

Regards,
Kleber