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

Reverse Proxy w/ Cognos 8 for the SUPER EXPERTS....??

Started by ktide09, 13 Aug 2010 05:20:11 PM

Previous topic - Next topic

ktide09

...for the web service pros...

have a reverse proxy through a firewall for external users accessing Cognos8.4. security ldap is series 7. namespace is good.The default.htm or Login page appears and attempts to authenticate when you enter the reverse proxy URL.  Users with the correct credentials attempt to launch cognos connection but gets looped back to the default or login page.  the login page keeps looping and not going to the cognos connection page.  Incorrect credentials get an invalid login attempt.  So that tells me it's properly reading the namespace.  IPF Log Viewer shows the sessionid is dropping and the details show the CDATA[not available]].  ..So almost like it's dropping the userid, perhaps by the rev proxy.(???)  within vpn going directly to cognos8 server, ..it works perfectly.  this only occurs to external users accessing the reverse proxy.

....here's what i think so far. all the services seem to require authentication. and i think there are 6 or so web services ...content manager, report delivery..etc.  So i'm thinking the CM Service is trying to verify session authentication and failing. but i'm not sure why.  perhaps the reverse proxy strips data during HTTP-SOAP requests.  i'm just not sure how...

any ideas from super cognos experts..?? 

ktide09

In addition...the URL after entering the reverse proxy address does change and access the cognos.cgi? and tries to perform the b_action..etc..

cognosjon


ktide09

that was the first thing we did. cognos Support does not technically "support reverse proxies"... that doesn't mean it will not work. Just means they either a.have not seen b.have not tried c.will not recommend and support.

ktide09

..late response.  fyi, this was resolved in Cognos 10.1 by using round robin DNS into the rev.proxy. thx!!