Results 1 to 4 of 4

Thread: Authorization

  1. #1
    Member
    Join Date
    Jul 2009
    Location
    London
    Posts
    14

    Authorization

    How does authorization work within Lightstreamer?

    Is it possible to restrict a client's access to certain item names within a subscrition? For example, we would like to prevent client A from seeing information pertaining to client B.

    Many thanks.

  2. #2
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,090
    All authorization stuff is performed by the Metadata Adapter.

    In particular, client requests for items are managed, first of all, by getItems, which interprets the request and can leverage the knowledge of the user name. Only the item names returned by getItems are attached to the session.

    Alternatively, if getItems only performs interpretation of the request at a syntax level, authorization can be delegated to notifyNewTables (see the caveats in the docs), which can veto an incoming request and send an error notification to the client.

  3. #3
    Member
    Join Date
    May 2010
    Location
    HCM
    Posts
    9
    Quote Originally Posted by DarioCrivelli
    All authorization stuff is performed by the Metadata Adapter.

    In particular, client requests for items are managed, first of all, by getItems, which interprets the request and can leverage the knowledge of the user name. Only the item names returned by getItems are attached to the session.

    Alternatively, if getItems only performs interpretation of the request at a syntax level, authorization can be delegated to notifyNewTables (see the caveats in the docs), which can veto an incoming request and send an error notification to the client.
    Could you post an example code?

  4. #4
    Administrator
    Join Date
    Jul 2006
    Location
    Milan
    Posts
    1,090
    There are no examples of authorization checks in the available demos.

    The following example code shows the use of notifyNewTables to check subscription requests and refuse them if needed.
    The methods shown should be added to the Metadata Adapter class.


 

 

Similar Threads

  1. Authorization on many exchanges
    By r9711465 in forum General
    Replies: 1
    Last Post: December 22nd, 2010, 11:54 AM
  2. Getting through IIS "Basic" authorization process
    By wmolde in forum Client SDKs
    Replies: 14
    Last Post: February 12th, 2008, 10:10 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 12:02 PM.