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.
I have written a servlet filter to set REMOTE_USER and configured WF for pre-auth. But when I attempt to get to my BIP I still get the sign-in page. Are there other session vars to set so that I can bypass the sign-in page?
Yes, have that turned off and so we get a 403 denied response back. It is like WFSERVLET is ignoring REMOTE_USER and the console settings to accept pre-auth. There section in the security manual called Configuring Pre-Authentication With Custom Single Sign On (SSO) Solutions really does not provide any specifics about admin console settings so we were hoping that some of the settings mentioned for pre-auth in other sections (like J2EE pre-auth) also needed to be set. For instance, In the filterPreference section of the file, set anonymousAuthEnabled to false, formAuthEnabled to false, and J2eePreAuthFilterEnabled to true (except we didn't do the last one since that was for j2ee auth). So maybe some of those other settings are not correct? Any suggests from someone who has implemented the custom SSO solution would be appreciated. Thanks! John
preAuthEnabled is expecting a header to contain the user id, not the remote_user. Manage the header in your request wrapper and add the header name to the security settings.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott