Focal Point Banner


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.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Require login for a specific report

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Require login for a specific report
 Login/Join
 
lmorgan
Member
posted
I am very new to creating procedures and reports. We have our reporting server on an AS400 system and using mostly DB2 files. We are using the AS400 security instead of setting up users in MR. We want to require a login for some of our HR reports and was wanting to know the best practice to use to accomplish this.


WF 764 on AS400
 
Posts: 3 | Registered: July 02, 2008Report This Post
TexasStingray
Master
posted Hide Post
To help get he right infor are you using IBM Web Query or do you have full blown WebFOCUS?




Scott

 
Posts: 865 | Registered: May 24, 2004Report This Post
Scott Broderick
Member
posted Hide Post
It appears that you are not using Managed Reporting at all, if you want security for certain reports in a self-service mode you can have them call the wfsignon.html page in the /ibi_html/ directory. This will setup a cookie with the security information for that user. You could also have embed some javascript in your html page to check for the cookie and then prompt them if it does not exist, so that is the click on a report that requires a u/p and they do not have the cookie set in their current session it will prompt them otherwise it will run. There a sample available on the internet of these types of javascripts. Hope this helps
 
Posts: 1 | Registered: November 14, 2003Report This Post
AlexU
Gold member
posted Hide Post
If it's only on certain reports you can add a parameter and evaluate the text entry on the launch page against a fixed value in the fex. In effect the text entry is a password for that report Somethin like:

-IF &PSWRD EQ 'password' THEN GOTO RUNREPORT ELSE STOP;
-STOP
Add message to user that password was incorrect.
-EXIT
-RUNREPORT
Rest of your Code

Or, add Javascript to the launch page's Text Entry box with a hard coded password in the script.


WF 7703M, XP/Win7, MRE, RC, BID, PMF, HTML, PDF, Excel 2000/7/10
 
Posts: 73 | Location: NY | Registered: February 06, 2007Report This Post
dhagen
Virtuoso
posted Hide Post
Just a thought, but:

Set up two WFRSs with a single WF Client. Have one of the WFRSs set with a service account so that the users could just run requests as required. Have the second server set up with no service account so that when a user requests a report from that server, they will be prompted for their logon credentials. If you make sure that the protected reports are only available on the "secured" server, then that will solve your problem.


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
GinnyJakes
Expert
posted Hide Post
dhagen's approach will work but may require additional licensing.

Another thing you can do is have one reporting server with security on. Using the the WF client admin console, create two client nodes, one with a default userid and password that the 'non-secure' reports will use (IBI_REPORT_USER and IBI_REPORT_PASS). Create another client node with no default id. You would then customize a copy of the wfsignon.html (as Scott suggested) to run your specific application and making sure that a hidden variable is IBIC_server pointing to your logical client node.


Ginny
---------------------------------
Prod: WF 7.7.01 Dev: WF 7.6.9-11
Admin, MRE,self-service; adapters: Teradata, DB2, Oracle, SQL Server, Essbase, ESRI, FlexEnable, Google
 
Posts: 2723 | Location: Ann Arbor, MI | Registered: April 05, 2006Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     Require login for a specific report

Copyright © 1996-2020 Information Builders