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.
How can you validate the user to EDASERVE prior to the Html Launch Page opening? The dropdown boxes are not loaded from datasources unless the EDASERVE is validated.. This only works if using a dual signon Group Dashboard(MRE & EDASERVE validated up front). I'd like to access this Launch Page from a URL outside of a Group Dashboard. Using WF 7.13
If you don't mind having the userid's for mre to be the same as the userid's required for the reporting server, you can change the mr security setting from the client admin console to use an External Directory or WFRS (WebFOCUS Reporting Server). The passwords in mre will now be ignored, and any single logon will authenticate the user at the server, then log into mre. That should solve your problem.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
You can proxy the credentials, and have the client pre-set the server connection using the IBI_REPORT_USER/PASS in the client admin console. Or you could try setting the WF_AUTOSIGNON to PREPROMPT. I don't know if it will help with the above question, but you could give it a try.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott