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.
Morning everyone, I am currently trying to hide the ibic_user and ibic_password hidden values on a html launch page.
Anyone know of a fairly simple way to do this, also not I am not the administrator so i think changing any files on the web focus server side is pretty much out.
When I run the page and "view source" the user name and password are viewed plain as day. I need to remove these from view but still be able to pass them to the servlet from the html launch page.
Any help would be greatly appreciated, thanks. JeffThis message has been edited. Last edited by: Erney,
If this is a permanent id for a connection to a data base, why don't you put the connect string to the DB2 connection in the global profile (edasprof.prf) and then encrypt it? Hard-coding the IBIC variables is like not having security on at all so use a default id to connect to the server (can set this up in the Remote Servers section of the WebFOCUS client console) and then a permanent set of credentials in edasprof to connect to the data base.
We ended up adding two more input boxes, one for the mainframe user and one for the mainframe password then pass them as the ibic_user and ibic_password.
This way, each user had to be assigned to the database table on our mainframe through our security department.
Basically, anyone can see the webpage and run the report if they knew the url but the report would return wrong username/password if they were not defined or added to the database.
That works, too. Just need to be careful about sending those credentials over an open wire (without https or some encryption) as they are sent in plain text by default as part of the URL string)
Regards,
Darin
In FOCUS since 1991 WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex WF Client: 77 on Linux w/Tomcat
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007