Saxo Plugin

Hello, i am trying to get the Saxoplugin up and running on a saxo liveaccount. I created a App in Simulation an one in Live on Saxo Developer. I can run eg. the downloadscript with an 24 our token on the simulatuon account. If i use the live app with auth i get this Error.
Download
Login 0 Saxo V2..
!AppKey and Secret detected.
!Authorization required.
!Launching browser for Authentication...
!Waiting for user to log in to Saxo Bank via web browser...
!Listening on http://127.0.0.1:31022/
!Acquired AuthCode.
!Login successful
!Invalid access token?
Can't connect!

Any ideas what i am doing wrong? Thanks in advance . Best regards bdgogo

Nobody using this Plugin? Maybe you need additional Information. The Logon completes in the Webbrowser without any error. I go through the Saxo 2FA logon and the the browser says Logon ok, close this window.
But the saxo plugin then does not connect. Changing the loglevel don't bring more information and there is no plugin log. Any help is very appreciated. Thankx

Did you configure your Accounts.csv file correctly? Refer to the following:
https://zorro-project.com/manual/en/saxo.htm

Thank you Andrew!
Yes, i think so because the plugin redirects me to the Saxo Loginsite and i can login there successfully. Here my Accountsentry. id and pw changed :-)
SaxoAuthlive,Saxo,EUR,ddbe1261cce1436b911cdb327xxxxxd,fed951bb100441ac9yyyyyyyabcb8888,AssetsSaxo,USD,1,14,Saxo

i also tried it with the SaxoToken entry and a 24h token. This works well but as far as i understand this works only with an simulation account and an permanent token is not possible for retail oder business accounts.

For the id and password in the accounts.csv i use the appid and the appsecret. In saxotrader log i see a successful application login.
I also updated the local saxotraderapp to the latest version on my Windows 11 PC

I found this in my notes regarding Saxo, so maybe the man page has bad info:

• Username is AppKey, password is the Secret.
• In the web portal where the app keys are stored, the URL redirect must specifically be set to “http://127.0.0.1:31022/”.
• It will need to launch a web browser, where the user must enter account credentials. It will hand a code back to Zorro.
• The refresh tokens expire after only one hour, so the user will need to log in every time they start Zorro.
• The good news is that the refresh tokens get automatically updated while it is up.
• The bad news is that if the servers go down for an hour, the user will need to log in to get it back up and running.

Hi Andrew, thank you for the list. This is exact what i have done. The redirect URL is also ok. As you can see in the attached screenshot.
Seems that it give back a code, but the plugin cannot interpret this. I have tried this also on a different Windows 11 pc and i am using Zorro S
Best regards Dirk

Set the LOGFILE flag and set the Verbose global value to 7 + DIAG and upload the log files. If necessary censor sensitive data.

Sorry , with this code at the beginning of the script :
function run()
{
Verbose = 7+DIAG+LOGMSG;
if(is(INITRUN))
{
set(LOGFILE);

}
...

There is no Diagnosticlogfile when i run in Trademode only in Testmode. And the normal Logfile contains the same information as posted at the beginning of the thread. I also tried to set the verboseflag in zorrofix.ini but the same result.

Hi, back to my initial question. Is anybody using this plugin and does it work with enabled 2fa? tnx

The ...diag.txt file is also generated in trade mode. Maybe you have a different Verbose setting elsewhere? You can also start Zorro with the -DIAG comman line option, it has the same effect.

Come to think of it, can LOGFILE and Verbose be set in the script before the first BrokerLogin() call? If not, then the commandline method is required.

Thank you jcl for the hint with the commandline option..
Very strange, after the update to 260.0.2 and no other changes on my system it now logs in without any problem. Thank you for the fix!!

Probably because there was a bugfix since your version.

Thank you for you help Andrew, i think you are right. Maybe there was a fix in this version or something on my system was fixed by the installation script.