Cannot connect to the stream with demo accounts

[SoftTrading]

Hello,
Since a few days, this application doesn't work anymore to connect to the stream with the IG demo accounts.
I think the problem comes from the IG lightstreamer servers, but I don't know where the problem is.
Do you have any idea?
Should I update the lightstreamer client?
Thanks

[teebeast]

I forked this project and fixed some things. See Issue #12. Maybe it helps you. I used it with my demo account from IG and it works. I updated Lightstreamer to the latest version, but it does not work with my IG account, only to version 5.0.5.

[SoftTrading]

Thanks for your help.
But taking into account your remarks the application still can't connect to the stream and the error message on 'Connect' is the following:
"Could NOT connect to Lightstreamer.Endpoint=https://demo-apd.marketdatasystems.com"

[teebeast]

I fixed it in my fork. Give it a try. I updated the nuget package from Lightstreamer.DotNet.Client to Lightstreamer.DotNetStandard.Client.

[SoftTrading]

I took Lightstreamer.DotNetStandard.Client in version 5.0.5 and it still doesn't work.
The error message is "the transport stream has been disconnected.

[teebeast]

I retested my Fork with my demo account and it's running fine. It is ready to test, when you change the account information in app.config.

I have not tested all aspects of this application, but basically it should work.

[SoftTrading]

@(teebeast) :

Thanks for your help.
I tried with your Fork but here is the message I get:

[teebeast]

Hm, I have no problems. It shows you a list of accounts? You have to set the key account in app.config, which is originally not required. The list of accounts shows it to you as account id. It must be a CFD account type.

Hope this helps.

[SoftTrading]

And now it works for the demo account but not for the live account.
Really impossible to understand at my level

[teebeast]

When you use your live account, your environment should also be "live" and not "demo". By the way, I have not tried any live account. The demo server uses another url than the live server. That might be the problem.

[ireay]

@SoftTrading did you get this working in the end in both environments? Note that the sample code keeps track of the context roots of each environment and then appends the rest of the URL onto the environment's context root.

The final point is that Tokens are issued per environment. So your program needs to keep track of the context root and then the tokens to put in any request header.

[Ketu748]

Is there any reason why context = IgRestApiClient.GetConversationContext(); isn't holding the values of cst and xSecurityToken?

[thompsont1962]

@teebeast
I cannot get the "fork" solution to connect lightstreamer and I cannot see how it could.
To connect to lightstreamer the xSecurityToken is needed, but this is not returned in a V3 PUT session authentication. Hence Ketu748's comment here

As the IG docs say
"The streaming API currently does not accept OAuth tokens so users holding OAuth bearer tokens should call GET /session?fetchSessionTokens=true to obtain CST and X-SECURITY-TOKEN tokens."
regards Tom

[teebeast]

@teebeast I cannot get the "fork" solution to connect lightstreamer and I cannot see how it could. To connect to lightstreamer the xSecurityToken is needed, but this is not returned in a V3 PUT session authentication. Hence Ketu748's comment here

@thompsont1962, I fixed it. The GET request /session?fetchSessionTokens=true was missing. In the end a simple line of code. In my own implementation everything is working fine.

[thompsont1962]

@teebeast ,
thank you for the committed fix
I inserted similar into the project and also got it working.

Do you know if there is a fork anywhere that used v1 or v2 authentication with this newer lightstreamer connection module?
If not I might experiment. IG's live and demo lightstreamer connections are currently at issue and I'm not sure if its V3 or the projects old dotnet LS dll . Given the IG LS companion seems to get the x-security-token from a v1 session (with a "PUT" to create the session) and it works, my feeling is that the the old dotnet LS dll is no longer up to it
regards Tom