Aeon Known Issues
9 results found
-
Using an nonexistent researcher username in the create request endpoint returns inaccurate validation messages
When using the create request endpoint, attempting to use a nonexistent researcher username as the reference when the RequestFor type is "researcher" returns inaccurate validation messages that do not make it clear that the user doesn't exist:
"{ResearcherUsername} is not a valid researcher username.",
"{ResearcherUsername} has been marked as an Anonymous user and cannot be a researcher username.",
"{ResearcherUsername} does not have a researcher association with {username}."Bug# 27504
0 votes -
Researchers cannot be associated with requests using the create request endpoint
When using the create request endpoint to create a request via the Aeon API, attempting to associate a researcher with the request via the RequestFor field will allow the request to be created, but Aeon will set the RequestFor field to the username associated with the request instead of to the researcher's username.
Bug# 27503
0 votes -
The Users/{username}/requests endpoint returns a 500 when setting activeOnly to 'true'
Setting activeOnly to 'true' when using the GET Users/{username}/requests endpoint to limit the requests returned for the user to only return those that are active results in a 500 error. Since the activeOnly parameter defaults to 'true', not setting a value for this parameter also returns a 500 error.
Bug# 27501
0 votes -
Activities cannot be associated with requests using the create request endpoint
When using the create request endpoint to create a request via the Aeon API, attempting to associate an activity with the request via the ActivityId field will always fail with the following validation message:
"User [username] is not associated with Activity [id]"
Bug# 27495
0 votes -
Aeon API can experience connection exhaustion with the database
The Aeon API can sometimes experience connection exhaustion with the database, which can lead to 500 errors in the API.
Bug# 26032
0 votes -
The Web API request creation endpoint does not properly validate an activity association.
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# 13748
0 votes -
Backslashes are not handled in the Aeon API for the username field
If a username contains a backslash, it will not be handled/returned by the Aeon API.
Bug# 12999
0 votes -
Aeon Web API reports invalid X-AEON-API-KEY header in logs unnecessarily
The ApiKeyAuthenticationMiddleware layer is invoked unnecessarily for non-secure endpoints, resulting in invalid X-AEON-API-KEY header log statements.
Bug# 10273
0 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