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.
When using a query string to run WebFOCUS reports, it's possible to pass a variable and value in the URL that can be decoded into a User Id and Password on the report server for authentication, like &APPNAME=SOMEVALUETODECODE.
I am wondering if there is some way to do the same thing when using a WebFOCUS Web Service...
The only way I have found is to explicitly pass the User Id and Password using the WebFOCUSLogOn function. But this requires that a User Id and Password be maintained on the client side (stored encrypted and then decrypted for the function call).
There is another way to authenticate without running WebFocusLogOn. The result of WebFocusLogOn sets an object called LogOnInfo. This object can be set with the Userids and Passwords and setting doSignon = true in this object. By doing this, any function run will authenticate with the credentials supplied in LogOnInfo before performing the function that it is being used in. Chapter 3 of the WebFOCUS Web Services manual documents the usage of the the LogOnInfo object.
Posts: 229 | Location: New York | Registered: July 27, 2004
It appears that setting LogOnInfo still requires a User Id and Password from the client...
What we're looking for is the ability to do decoding of a User Id and Password on the reporting server by passing a variable and a value, as in the query string example in the original post.
I don't think I understand fully what you're asking. Can you explain in detail what happens when you pass this value to decode in a URL. How is this value getting decoded and what is the Userid and Password being used for post the decode. Are you calling a FEX to do the decode in the original request?
Posts: 229 | Location: New York | Registered: July 27, 2004