As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at email@example.com for further assistance. Reference the community FAQ to learn more about the community.
We bypass this issue in a few ways. One method is to create a public dashboard for reports that can be ran without loging on first. The problem with this of course is that everyone that has access to webfocus can run these reports.
Another is that these reports are created on the report server and ran outside of MRE the security is take care of by the portal that was developed by the application area.
And Third we are implementing Single sign on so that managed reporting will pick up the id the person used to log in to their workstation for authentication and authorization. However this does involve software from a 3rd party.
Webfocus 8.0.7 on Windows
Posts: 176 | Location: Ohio | Registered: October 26, 2006
Stefan, If the credentials are the same between SAP and WebFOCUS you could trigger a WebFOCUS or Dashboard sign-on via an AJAX call behind the scenes at the same time the user logs into SAP. Otherwise you have to do some type of integration.
The following document outlines some of the considerations and the general process flow I've seen people use when doing integrations like this:
At this point in time WebFOCUS only supports a single mode of authentication.
This gives you two options to stay within that framework: 1) Have two WebFOCUS Clients with different security configurations. (Requires two WF Client licenses)
2) Have two different web-server tier's that have different options for setting REMOTE_USER, both web-tier's pointing to the same WebFOCUS Client.
e.g. Have IIS as one entry point where REMOTE_USER is populated by the IWA security against AD, and have your custom software be another entry point that also populates REMOTE_USER based off of the authentication it does, and sends the user directly to Tomcat