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.
Our installation of wf has never had the need for security other than who may access the portal. We do have a need now to shield the results of a pop up report on a particular tab from certain users.
My simplistic approach was to add a prompt for a password, white font the users entry, shrink the font down so no one can highlight it to see thru the white font. Then we just give out the password to those who need it. Of course the fex does a check against the pw before running the report etc...
It works but having shrunk the font down so much looks weird and if I enter the pw wrong, it sometimes makes reentering it an issue if I do not delete my old entry.
Is there anyway I can have the pw entered in a normal font but display '#' signs or something for the characters so no one can see what the users types?
BTW, I am open to any other idea on protecting this single report.
We are on WF 8.This message has been edited. Last edited by: FP Mod Chuck,
Using WF8 security model you can grant or not access to user group or specific user(s) so why would you like to add a password protection on report execution ?
If the user/group doesn't have access to the report it won't popup (except if I'm totally wrong about WF8 security).
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
...shield the results of a pop up report on a particular tab from certain users...I am open to any other idea on protecting this single report...
Do you have a list of users who have authority to access the classified report?
If so, perhaps test the incoming User Id against the list, showing the report if the user is on the list, and a 'Sorry' message, if they are not on the list?
I have our public dashboard published on our intranet , therefore access is restricted to our company users.
To run the reports you are prompted for a password which is an &variable.
I have a define which selects the ‘Department’ to report from depending on the &variable value. The define is standalone and is referenced in the reports using an include.
My simplistic approach was to add a prompt for a password, white font the users entry, shrink the font down so no one can highlight it to see thru the white font.
Hi Robert,
If this is the way that you intend to go, then no need to jump through hoops to protect the viewing of the password, just change the "type" attribute for the input control to "password".
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
You need to ask yourself/managers what is the impact to our company if the report is view by someone who should not be able to see it. If it is minimal then your approach may be all you need. If it is anything else then you should use the security built into the product. ESPECIALLY because you said the public portal in on the INTERNET.