Aeon Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 400 Bad Request error handling is insufficient when using the request creation endpoint.

    When the request creation endpoint encounters a 400 Bad Request error, a generic error message is returned that does not contain sufficient detail describing the problem.

    Bug# 13747

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  3. The Web API caches some database values beyond the scope of a web request.

    When making changes to an Aeon configuration via the Customization Manager, the Web API will continue to use cached values in some instances beyond what is needed to process the current request until the app is restarted in IIS.

    Bug# 13746

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  4. Request creation validation error message is inaccurate when the specified researcher user doesn't exist.

    Creating a new request via the request creation endpoint that specifies a non-existent researcher will correctly return a validation error stating that the researcher's username does not exist, but will also incorrectly report that the format, serviceLevel, and shippingOption values are invalid.

    Bug# 13743

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  5. Custom fields of the 'Transaction' context type break API routing

    Using a custom field with the context type set to 'Transaction' in the CustomFieldDefinitions table breaks routing through the Aeon API and returns a 500 error.

    Aeon v5.1

    Bug# 13642

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  7. Missing validation for activities in transactions

    In TransactionValidator, there is no validation for ensuring that ActivityId and ResearcherUsername are mutually exclusive or that the user is associated with the activity.

    Bug# 11562

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  9. TransactionValidator creates some redundant and/or incorrect error messages

    For example, validating a transaction without username results in the following:
    2x "username can't be empty"
    1x " is not a valid username"
    1x "user cannot be anonymous"

    Bug# 8889

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Aeon API  ·  Flag idea as inappropriate…  ·  Admin →

Feedback and Knowledge Base