scadaadmin6.1 under wine produce difference token?

Forum Home Forums Development and Integration scadaadmin6.1 under wine produce difference token?

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #13167
    zzz
    Participant

    The influxdb token uploaded from scadaadmin6.1 on wine 8.3
    becomes a totally different token sent by rs6 to influx (checked via tcpdump -i lo port 8086 -A on server).
    Re-uploading the same token from scadaadmin6.1 on windows works just fine.

    The * mask makes debugging such issue very frustrating, since once pasted or typed, you never know if you have typied sth wrong or sth weird elsewhere in the chain happened, they are either masked or hashed, there is nowhere to verify.

    • This topic was modified 2 years ago by zzz.
    • This topic was modified 2 years ago by zzz.
    #13170
    zzz
    Participant

    I edited the code, and recompiled to show masked string in log. Right now, I can’t replicate. Weird.

    #13172
    Mikhail
    Moderator

    What was the cause of different ScadaAdmin behavior?

    #13178
    zzz
    Participant

    I can’t replicated after wine scadaadmin.exe restarted. I usually put laptop at suspend after work, that instance of scadaadmins on wine has run for more than a week or so. A wild guess sth. internally might have corrupted in previous operations, a restart just fixed it.

    There are two possibilities, either it submitted wrong token, or it failed to update the config, either way, after several upload attempts from scadaadmin on wine, I can see in tcpdump RS6 server is sending some unknown token to influxd.

    Previously I deleted the token RS6 used before. since it was using my admin token, and in influx web there is no way to see existing token ( You can see all tokens in influx CLI, but that requires you to have an admin token first 🙁 ), web console only allows rename/delete, a bit like in scadaadmin. Thus I can only delete and recreate a new admin token and create a new customized token for rs6 for writing.
    So I can’t say if the unknown token in tcpdump is from previous old config (a failed to update issue) or an mis-encode/decoded token (as was suspected from previous post) but either way, there is something weird happening, since everything is masked, I can’t say what exactly happened for sure…

    Just posted here for caution when using scadaadmin with wine , and raising awareness of the inconvenience of mask everything up approach.

    #13182
    zzz
    Participant

    I got it. I switched scadaadmin to ExtDepPostgreSql, I though the server will be affected by this change and neglected, this actually does nothing server side. so false alarm, on the wine stuff. Masked secrets are still a pain for debugging.

    #13185
    Mikhail
    Moderator

    Thank you for the info.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.