-
March 10th, 2010, 12:20 PM
#2
Lightstreamer does not perform client authentication on its https connections,
nor does it forward the client X.509 certificate to the Metadata Adapter upon session initiation requests; the latter might be a feasible extension.
Request to the client for HTTP authentication is also not supported.
If your client can manage to force the inclusion of the certificate in the request header of all the http or https requests performed by the client library
(like a cookie, but, preferably, not as a cookie),
then your Metadata Adapter will receive it (only upon session initiation requests) in notifyUser, beside username and password, through the httpHeaders parameter.
Otherwise, the certificate would have to be embedded in some way into the username or password field.
Similar Threads
-
By karthik655 in forum Client SDKs
Replies: 3
Last Post: May 3rd, 2012, 10:07 AM
-
By exchangepulse in forum Adapter SDKs
Replies: 2
Last Post: March 19th, 2009, 07:37 PM
-
By stephenlam in forum Adapter SDKs
Replies: 4
Last Post: December 12th, 2008, 10:52 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 01:50 AM.
Bookmarks