Skip to content

Aeon Known Issues

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

7 results found

  1. Aeon API logs are not sufficiently detailed for troubleshooting certain web client issues

    The Aeon API log does not contain sufficiently detailed logging statements for troubleshooting certain issues in the Aeon Web Client, for example, when a user's multifactor authentication configuration fails.

    Bug# 28355

    1 vote

    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  ·  Admin →
  2. Researchers cannot be associated with requests created via the create request endpoint

    Setting the RequestFor type to "Researcher" always returns a 500 error when attempting to create a request via the create request endpoint in the Aeon 6.0 Web API, regardless of whether or not the researcher username given is valid.

    Bug# 27516

    1 vote

    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  ·  Admin →
  3. Appointment Status can be set to an invalid value using the appointment creation endpoint

    The Appointment Status field can be set to any value using the appointment creation endpoint in the Aeon 6.0 Web API, which can lead to appointments created with invalid statuses.

    Bug# 27514

    1 vote

    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  ·  Admin →
  4. 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

    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  ·  Admin →
  5. 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  ·  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  ·  Admin →
  7. 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  ·  Admin →

Feedback and Knowledge Base