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.
"There was an issue reviewed by the Product Division as follows: WF8ashboard:Unable pass in URL Username/Password
Passing credentials on the url is seen as a security vulnerability, as web servers typically log url information.
User's will now be required to pass credentials. I believe starting the Reporting Server unsecured is not an option."
That may not work for us because we have WF reports and dashboards with our existing web portals which already have AD login screen of its own and we are not going to ask user to login again on WF server with same credentials. I am pretty sure they might have thought about that before putting that kind of restriction in WF 8 security model.
If you already have AD set up for other web sites, then you should be able to easily set up Single Sign-On (SSO) using IWA or LDAP.
Are your WebFOCUS IDs the same as your AD IDs? If so it's simple. If not then you can probably run the Reporting server trusted and pass the AD id from your other login pages.
Cheers
Stu
WebFOCUS 8.2.03 (8.2.06 in testing)
Posts: 253 | Location: Melbourne, Australia | Registered: February 07, 2007
Unfortunately you are probably have to read the Security Manual for Version 8 (specifically Chapter 7. Authentication), but a quick overview for a SSO deployment on Windows
1. Set IIS to use Windows Authentication 2. Change Tomcat to not do Authentication - add tomcatAuthentication="false" to your AJP connector After these two steps you should be see the REMOTE_USER populated with your AD id in the WebFOCUS Client admin Console - under Diagnostics -> HTTP Request Info 3. Make sure that your Reporting Server is configured for LDAP/AD (or OPSYS if on Windows) and you can log in with your AD id. 4. Change the WF client security to WFRS via Admin Console 5. Restart tomcat and see whether you can log in with AD id. If you get this far then you can alter the securitysettings.xml to turn of the login form and pass REMOTE_USER as the login ID. Once this works the next step is to change the connection from WebFOCUS client to Reporting Server to be trusted nad you should no longer be prompted for credentials against the Reporting Server.
Do this on a WebFOCUS install that is not using IIS is a little more complicated but you just need to identify what header your SSO is setting if it is not REMOTE_USER.
Feel free to ask any specific questions you may have. All environments have their own "weird" points that makes security a non-trivial task.
Cheers
Stu
WebFOCUS 8.2.03 (8.2.06 in testing)
Posts: 253 | Location: Melbourne, Australia | Registered: February 07, 2007