About Environments in API Manager (Nov 2017)
The support for environments in strategic components of Anypoint Platform eliminates the need to construct version names to reflect an environment. The administrator grants permissions per environment. A user who is granted environment access permission has full access to operations inside the specific environment:
As administrator, you grant permissions to users as described in the topic linked below.
When you navigate to API Manager, you see the environment control bearing the name of your default environment on the upper left. In this example, Sandbox is the default environment:
When you click the environment control, a list of your environments appears.
To connect Mule Runtime to API Manager, you need to provide the client ID and secret from the environment where you registered the API.
If you upgraded APIs from the earlier versions of API Manager to the November 2017 release, you might have APIs residing in the Unclassified environment. Other APIs that you haven’t associated with an environment, such as an API you create in Design Center, published to Exchange, and set up to manage from Exchange also appear unclassified in API Manager. You need to classify an API to manage it. Until you classify the API, the user permissions under the earlier release apply to all operations. After classification, the permissions per environment that you grant to users applies.