Results 1 to 10 of 16

Hybrid View

  1. #1
    Member
    Join Date
    Apr 2007
    Location
    Kerry
    Posts
    17
    Thanks Dario.

    The MBean strategy works perfectly for us.

    The reason why we want to kill the user session is not really related with having multiple sessions (I guess to solve this overwrite the newSession callback method in the adapter is more than enough) but with security. Our system has a built-in hard session expiry mechanism to prevent malicious session handling attacks.

    Having the JMX possibility is enough for us. Btw, is the JMX server secured? Because if it stores the session as it seems I guess that you can obtain plenty of useful information from it.

    Regards,
    Martin

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,091
    Hi Martin

    may you please clarify your security concerns?
    We aim to guarantee security against external hosts. The JMX interface is exposed through some configurable ports, which can be hidden by the firewall and this should be enough.
    However, at the moment, we don't protect the Server (and, in particular, its JMX interface) against its own Adapters. We consider the Server and all configured Adapters as "friends". In fact, they all lie in the same ClassLoader.

    Dario

  3. #3
    Member
    Join Date
    Apr 2007
    Location
    Kerry
    Posts
    17
    Hi Dario.

    The problem is not the adapter but an attacker from outside that box, even within the green zone. You can enable some firewall rules to protect you from external attackers but within your intranet probably your sysadmins will want to be able to use the JMX console wherever they are.

    As far as I know, there is no authentication for the JMX RMI interface so anyone that is in the intranet can open a JMX console and kill other user's sessions. Correct me if I'm wrong as I haven't tried it so it is only speculation.

    Anyways, not a big issue for as and I suppose it could be an improvement.

  4. #4
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,091
    Hi Martin,

    Indeed, such a protection in the JMX access is lacking.
    The extension is in our roadmap, but no time references have been set yet.

    Dario

  5. #5
    Member
    Join Date
    Apr 2007
    Location
    Kerry
    Posts
    17
    Thanks Dario,

    that's good to know.

    Is there any reason why Lighstreamer is using its own JMX server implementation instead of using the JDK Platform MBean Server?

    Martin

  6. #6
    Administrator
    Join Date
    Jul 2006
    Location
    Milan, Italy
    Posts
    521
    Hi Martin,

    Lightstreamer Server uses Sun's MBean Server (in particular, Sun's JMX Reference Implementation and Sun's JMX Remote API). You can find the related JAR files under "\Lightstreamer\lib".

 

 

Similar Threads

  1. Forcing session termination
    By Alessandro in forum General
    Replies: 6
    Last Post: February 7th, 2020, 02:03 PM
  2. disconnection problems
    By magnum_rg in forum Client SDKs
    Replies: 5
    Last Post: August 12th, 2011, 09:43 AM
  3. Track the Server disconnection
    By vaduganathan in forum Client SDKs
    Replies: 1
    Last Post: May 12th, 2010, 09:26 AM
  4. System.Security.SecurityException
    By gjoseph in forum Client SDKs
    Replies: 3
    Last Post: August 20th, 2009, 10:14 AM
  5. Internet Explorer --> Security zones issue
    By Mone in forum Client SDKs
    Replies: 0
    Last Post: July 30th, 2009, 09:09 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 07:18 PM.