put_submodel_element_by_path_submodel_repo Authentication Credentials Get Lost

[michakoebele]

When calling put_submodel_element_by_path_submodel_repo, the authentication data is lost somewhere inside the function chain. As a result, the request is sent without credentials, and the server rejects the update operation.

GET requests work because they do not require authentication, but both PUT and PATCH fail due to missing credentials.

While debugging and stepping into the function calls, the credentials object is still present at the beginning but becomes empty after several nested calls.

This indicates that authentication data is not forwarded correctly somewhere inside the internal function chain.

[zrgt]

• Which version of the client do you use?
• Where exactly do you provide auth credentials? Could you provide a code snippet, so that we can reproduce the issue?

[michakoebele]

I'm using the latest version of the client.

[zrgt]

@michakoebele could you provide headers of the request and the response of the server?
You could debug the code and set a breakpoint at the line 172 in https://github.com/zrgt/aas-api-python-client/blob/f11de66c2d9e2c0634a3666dbfaca184402e83c1/aas_python_http_client/api_client.py
Here you will see all raw data used in the request

[michakoebele]

This is the response of my code:
25-12-09 07:04:39 [ERROR] [020_write_operational_data] [] - Error accessing Submodel: (401)
Reason: Unauthorized
HTTP response headers: HTTPHeaderDict({'Server': 'openresty', 'Date': 'Tue, 09 Dec 2025 06:05:29 GMT', 'Content-Type': 'text/html', 'Content-Length': '176', 'Connection': 'keep-alive', 'WWW-Authenticate': 'Basic realm="Authorized users only"', 'Strict-Transport-Security': 'max-age=63072000'})
HTTP response body: b'\r\n<title>401 Authorization Required</title>\r\n\r\n

401 Authorization Required

\r\n

---

openresty\r\n\r\n\r\n'

This is when I set the breakpoint at the line 172:

And the authorization is in "config".

[zrgt]

I could not reproduce the issue. I've run the same code and I have Authorization in params. Please ensure you are using the latest verion of the client which is 1.0.2