5 results found
The Aeon API can sometimes experience connection exhaustion with the database, which can lead to 500 errors in the API.
Bug# 260320 votes
If a request is created via the request creation endpoint, validation will not apply to enforce that the username on the request is associated with the specified activity ID.
Bug# 137480 votes
If a username contains a backslash, it will not be handled/returned by the Aeon API.
Bug# 129990 votes
The ApiKeyAuthenticationMiddleware layer is invoked unnecessarily for non-secure endpoints, resulting in invalid X-AEON-API-KEY header log statements.
Bug# 102730 votes
Web API requests fail due to multiple requests from different applications being processed simultaneously
Requests to the Aeon API from multi-threaded applications are failing to be served by the API. Requests are failing due to a "missing" API Key despite it being provided in the header.
Sample error message in Aeon API logs:
INFO AtlasSystems.Aeon.WebApi.Security.ApiKeyAuthenticationMiddleware - ApiKey was not authenticated. Failure message: Unable to authenticate API key.
ERROR AtlasSystems.Aeon.WebApi.Security.ApiKeyAuthenticationHandler - Error retrieving web platform config: <APIKEY>. The context cannot be used while the model is being created. This exception may be thrown if the context is used inside the OnModelCreating method or if the same context instance is accessed by multiple threads concurrently. Note…0 votes