Closed iosb-ina-mr closed 1 week ago
Today, I experimented with the AASX Package Explorer along with the server for the first time. Although I can run the server locally and see the assets, I get a 403 error when I try to connect to the repository. Is there possibly already a solution or any tips?
We have the same problem. The API call still worked in the main branch a few months ago. Swagger UI: Request: http://172.16.163.253:5001/packages Response body: { "Messages": [ { "Code": "Forbidden", "CorrelationId": null, "MessageType": "Error", "Text": "Cannot proceed as decodedAasId is null", "Timestamp": "09/16/2024 12:12:58" } ] }
Hi, aasx server has been having problems with the API because of some changes to dotnet8... It's being worked on but for now I would suggest to download an earlier release : (
Describe the bug
The API endpoint "GET /packages" is not working anymore for the latest aasx-server-blazor-for-demo:main. Since I can't find any version number, here is the timestamp of when it was released on docker hub: Jul 25, 2024 at 1:09 am. I have attached the error log below. Even when I provide an AAS-ID (base64-encoded), as advised by the error response, a different error is returned.
To reproduce
Deploy the current version of the aasx-server-blazor-for-demo container, open the swagger UI and trigger the GET /packages endpoint.
Expected Behaviour
When no AAS-ID is given, the list of all AAS-IDs should be returned including their package-IDs.
Version
adminshellio/aasx-server-blazor-for-demo:main
Operating System
Linux
Relevant log output