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.
Hello, Working on implementing custom security filter... I ran into an issue.
Issue: Want to invalidate user session upon click on logoff in Dashboard. Below is the code..When user clicks on logoff in BID banner.. uri doesn't see "/logoff" in request submitted to WF Client. All I see is "http://servername/ibi_apps/controller" in request. How to capture/catch logoff action in BID?
any suggestions would be helpful.
String uri = httpServletRequest.getRequestURI(); if (uri != null) { if (uri.indexOf("/logoff") >= 0) { session.removeAttribute("IBUser"); httpServletRequest.getSession(false).invalidate(); return; } }
WF Client Environment: WF 7703 ThanksThis message has been edited. Last edited by: <Kathryn Henning>,
Prod: WF 7.6.10 windows. -- MRE/Dashboard/Self Service/ReportCaster - Windows XP
Posts: 82 | Location: Chicago | Registered: September 28, 2005
I believe the log off already invalidates the session. What you should focus on is invalidating the session when it is a new logon from the same machine when the previous user does not logoff properly. I usually do the invalidate as part of the logon. If the IBUser parameter NE IBUser attribute, then invalidate.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott