nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Single sign on across multiple servers

ckb

We have implemented single sign on using a cookie. The Actuate BIRT viewer and our calling application are on the same server but in separate contexts and this is working well. I want to move the BIRT viewer to a separate server. When I do this, the actuate.initialize() method fails. If I use a url of https://server:8443/ActuateJavaComponent the error returned says, "Error connecting to URL.". If I use a url of http://server:8080/ActuateJavaComponent the error returned says, "Authentication failed." Both of these url's connect to the BIRT viewer if I enter them in a browser.

We used the information in the article http://www.birt-exchange.org/org/wiki/index.php?title=Security_Integration_with_the_Actuate_BIRT_Viewers. We have overridden the LocalSecurityAdapter with our own SimpleSecurityAdapter which extracts user information from a cookie.

Find more posts tagged with

Comments

chavez_ant

I'd also like to get information on preventing the above errors with single sign-on in place, where the server of the web application is separate from the server running Actuate. If anyone in the community can help point us in the right direction, or give any tips for this situation, it'd be greatly appreciated.

Thanks in advance,
A. C.