[Amadeus-22]

Fixes #569.

Problem

After a WebSocket API connection is renewed, session_re_log_on re-sends session.logon built with api_key=False, skip_auth=True. With those options ws_api_payload only adds timestamp, so the logon goes out without apiKey and signature:

initial logon params: ['apiKey', 'signature', 'timestamp']
re-logon params:      ['timestamp']

The server answers -1102 Mandatory parameter 'apiKey' was not sent, but the client sets is_session_log_on = True anyway and stops signing the requests that follow.

Change

• session_re_log_on now builds the payload with api_key=True, skip_auth=False, the same way the first logon is signed: apiKey, a fresh timestamp and a new signature.
• The stored request's params are copied before signing, so the saved logon request is not modified and each reconnect signs from a clean copy.

Tests

Added TestSessionReLogOn in common/tests/unit/test_websocket.py:

• the re-logon carries apiKey, timestamp and signature;
• the stored request is unchanged after two re-logons;
• nothing is sent when the session is already logged on.

The first test fails on master and passes with the change. pytest tests in common/ passes (375 tests). The new test code is formatted with black.

Not included

is_session_log_on is still set as soon as the message is sent, without waiting for the server's reply. Setting it from the response would be more correct, but it changes the reconnect flow, so I left it out of this fix. Happy to follow up if you want it.

🤖 Generated with Claude Code