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.
Apps ask you to log in then the Login info is stored as a cookie in encrypted form and used without prompting the user everytime the server is referenced.
Occasionally you get reprompted and it seems to be when comms between the client and wf server deterioriates so that a response is not generated in a timeout period.
I have noticed that after a network failure the servers become reluctant to communicate (bit like people after failed relationships) and this can be cured by rebooting the server. Why this is so I don't know is it a Windows or wf thing.
These are gut feelings rather than empirical evidence but I would be interested to share others view on this topic.
Thanks
John
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
I asked one of our security experts about this one and here is what I hear back.
While it is difficult to actually tell from this what the exact problem is, the WebFOCUS security cookies for MRE and Self Service are set until end of session, unless a specific cookie expiration was setup during install and configuration. That said, when you say you are being prompted again, is it a WebFOCUS prompt or a Windows prompt? It sounds like a Windows thing, but if the cookies can change the URL, it might be causing the problem.
For example:
If the signon request happens against this server. http://test.mycompany.com/ the cookies will be sent to the test.mycompany.com every time the browser sends a request to that specific domain name. If this request is send http://test/... Then it will not send the cookies.
Here are thing you may want to look deeper into.
Hope this helps.
Cheers,
Kerry
Kerry Zhan Focal Point Moderator Information Builders, Inc.
Posts: 1948 | Location: New York | Registered: November 16, 2004