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 community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
You can use Single Sign On (SSO) with pre-authentication. This is described in the Security and Administration manual which is available at the WebFOCUS 8 InfoCenter.
In WebFOCUS Security and Administration Release 8.0 Version 08 is ‘Configuring Pre-Authentication With Custom Single Sign On (SSO) Solutions’ on page 235. Because we don't know anything about your web application with login, we can't yet give an answer if it is possible.
I had to go another way, with java, so that I could get it working.
So now I have a filter that does the job...
Steps:
1. configure isapi redirect for tomcat in IIS machine. 2.asp.net webapp after login create a cookie 3. create a filter( .jar) that checks the cookie and if ok pass a header with username..
Bruno, It is great to see that you were successful using the servlet filter approach. I have written a filter following the info from dhagen and that executes fine and sets REMOTE_USER, but I still end up at the signin page. Did you also configure WF for pre-auth? If so, what did you configure specifically? From the filter, what header var did you pass? Did you set a session var or a query string var? Thanks for sharing! John
We got some help from Webfocus tech support: Per our streaming session with you, these are the changes we made: securitysettings.xml anonymousAuthEnabled set to false
formAuthEnabled set to true (this allows the form to be accessed directly by url - http://server/ibi_apps/signin) set this value to false to disable the login page entirely.
preAuthEnabled set to false j2eePreAuthFilterEnabled set to true (this setting tells WebFOCUS to retrieve the value of REMOTE_USER and use it for authentication)
From the WebFOCUS Administration console we made one change to the odin.cfg configuration file. We changed: http://server/ibi_apps/ Administration -> Administration Console Reporting Servers -> Remote Services Select the EDASERVE bullet and click modify We changed the SECURITY setting from Advanced... to Pass WebFOCUS User ID and their Groups
Once we did this, WebFOCUS began picking up the hard coded value of your own userid that you had specified within your servlet filter code (we are setting REMOTE_USER).
We followed the above instructions and our filter started working. We did use the WF-provided wrapper code for the helper methods on the request vars. I expect you can get that zip file by contacting WF.
I think the key item that was not documented in the Security manual was turning preauth off and then turning the j2ee preauth on. The manual actually tells you do to the reverse of that for custom pre-auth.
I did the same setup to configure custom security filter in WebFocus 8.2. Once formAuthEnabled set to true, I ran into another issue - it often goes to the login windows instead of report parameter page. To make application work, so we disable formAuthEnabled.
but without form login, we are unable to access admin console to import/export reports.
then how do we prevent this?This message has been edited. Last edited by: yehf,