Forum Discussion
add /browerWeb Extension after domain name
- Aug 03, 2023
Nompang Button clicks should be handled on the website rather than the F5. They can make it so when the button "get" is clicked it sends a redirect path to them. This doesn't seem like it should occur on the F5 at all. Same goes for the first redirect. If they must perform the first redirect on the F5 you can do the following.
when HTTP_REQUEST priority 500 { if{ ([HTTP::host] == "www.abc.com") && ([string tolower [HTTP::uri]] == "/") } { HTTP::redirect "https://www.abc.com/browserWeb" } }
Aaron
How about eliminate this issue, by restricting the users to limited sessions using "Max Sessions Per User"?
On cli
can be used to filter the session id belong to a particular user and pipe to delete it. But that is resource intensive.sessiondump -allkeys
An extreme option is to delete all sessions something like:
sessiondump -list | awk '{ print $1}' | xargs -L 1 sessiondump -delete'
- coriolis_75734Mar 09, 2015
Nimbostratus
Limiting the max number of sessions per user wouldn't help in the situation where a user account has been compromised and being used by an unauthorised third party.
We do not wish to kill all sessions and ideally I'm looking for a solution where I can give the operations team a script to run which just requires a username input and the specified user's sessions will be killed.