Description of problem:

The following Satellite API endpoint, referred to in the documentation, returns the activation keys of other lifecycle environments, even though the environment is part of the URL path:{}

# curl -Ss -u "$auth" 'https://satellite.example.com/katello/api/environments/<env_ID>/activation_keys?content_view_id=<CV_ID>'

{}The expectation is that the above API call returns only the activation keys associated with the lifecycle environment specified.

Refer to the following KCS for more details:  https://access.redhat.com/solutions/7136605

How reproducible:

Always

Is this issue a regression from an earlier version:

No.

Steps to Reproduce:

Use the following Satellite API endpoint to list the details of the activation keys associated with a specific lifecycle environment:

# curl -Ss -u "$auth" 'https://satellite.example.com/katello/api/environments/<env_ID>/activation_keys?content_view_id=<CV_ID>'

Actual behavior:
The API responds with the details of all activation keys in the organization.

Expected behavior:

API call returns only the activation keys associated with the lifecycle environment specified.

Business Impact / Additional info:

1. Confusion to the user.
2. Could break some automated workflows that use the referred to API endpoint, for example, breaks the workflow to provision systems via Satellite.