BMW hat leider viel umgestellt
- BMW adds in the Approov SDK to their client and server.
- Before any request is made, Approov SDK (that is intentionally made as hard to reverse engineer as possible) runs attestion on the device. It uses Android/iOS internal APIs to generate a signed token that basically verifies that the device is not rooted or tampered in any other way. AFAIK this is the "Play Integrity Framework" on Android that has not been reverse engineered.
- Client sends that token and device/package information to the Approov server, which validates it and sends an another token back
- Client then uses that token as "Attestion token" on the client. It's most likely really short lived.
Damit kann man keinen eigenen Client mehr bauen.
Der Thread dazu ist hier:
BMW Connected Drive - Requires continuous re-authentications and still, errors for Login requires captcha validation · Issue #152646 · home-assistant/core
The problem BMW Connected Drive - Requires continuous re-authentications and still, errors for Login requires captcha validation What version of Home Assistant…
github.com
Eine Lösung ohne Befehle senden zu können:
GitHub - JjyKsi/bmw-cardata-ha
Contribute to JjyKsi/bmw-cardata-ha development by creating an account on GitHub.
github.com