ACARS Provider SayIntentions is not correct validated

[Revyn112]

Simulator Version

2020

Aircraft Version

Stable

Build info

{
    "built": "2026-01-04T18:35:07+00:00",
    "ref": "refs/heads/master",
    "sha": "4569ac848ea98bd0b1dbfad5b68f805408cdf672",
    "actor": "heclak",
    "event_name": "manual",
    "pretty_release_name": "master:4569ac84",
    "version": "a32nx-v0.15.0-dev.4569ac8"
}

Describe the bug

The ACARS ID for SayIntentions will not be validated correct. You can put literally anything as logon code and you will get { ok } as response.

Expected behavior

SayIntentions ACARS ID will be proofed by correct endpoint.

Steps to reproduce

1. Switch ACARS Provider to SAI
2. Set wrong ACARS ID
3. Get Successfully Validated Message

References (optional)

To validate SAI Keys you need to use correct endpoint

Additional info (optional)

No response

Discord Username (optional)

Revyn112

[Saschl]

Yes, seems like the ping endpoint (which we use for Hoppie to validate the userid) does not actually need a logon code. I reached out to find out if that's intentional. If it is, then we'll probably need to change to poll or something.

Thanks for reporting (and the PR, will look at it )👍

[tracernz]

Ones of the reasons we decided to go ahead with this was on the proviso that it's 1:1 Hoppie compatible and wouldn't impose any additional maintenance burden. Maybe we should re-evaluate if that's not the case.

[daveblackuk]

I am the SI dev for ACARs.

The Hoppie documentations does not appear to state that ping is used to validate a logon, but rather to determine if a callsign is online. We therefore do not protect this specific call with a credential, and does not infer non-hoppie compliance.

We a provide a dedicated validate Userid endpoint that is used by other devs, happy to share if someone DM's me.