Hi,
I'm using AIO Java SDK which uses OAuth Credentials and setting Environment variables.
Its working for Non prod and Prod.
But how to restrict the OAuth API Credentials to work only for Prod.?
Thanks,
Bhargav
Solved! Go to Solution.
Views
Replies
Total Likes
Correct Answer:
Open the AEM Cloud Service Developer Console by accessing the URL provided by your AEM Cloud Service environment.
Log in to the Developer Console using your Adobe ID credentials.
Once logged in, navigate to the "API Credentials" section or a similar section that allows you to manage API credentials.
In the API Credentials section, you should see a list of existing credentials or an option to create new credentials. Locate the credentials for which you want to assign a non-prod environment profile.
Edit the specific credentials you want to assign a non-prod environment profile to.
Look for an option or field that allows you to specify the environment profile for the credentials. It might be labeled as "Environment Profile" or similar.
Select the non-prod environment profile from the available options. The exact names and options will depend on your AEM Cloud Service configuration.
Save or update the credentials to apply the changes.
By assigning the non-prod environment profile to the API credentials, you are specifying that these credentials are intended for non-production environments, such as development or testing environments. This can help differentiate and manage credentials specifically for non-prod environments within the AEM Cloud Service Developer Console.
hello @bhargavthogata111
In what context are you using the OAuth credentials from https://developer.adobe.com/console in AEM?
I have created a custom Maven plugin (Ex: as in https://www.baeldung.com/maven-plugin) and i'm using aio-lib-java-cloudmanager ( https://github.com/adobe/aio-lib-java-cloudmanager/tree/main ) maven dependency in POM and used the OAuth credentials created in developer console in this SDK .
In Bamboo i'm using Maven task and configured this maven plugin. I'm reading client id, client secret from Bamboo variables.. Able to set environment variables, run pipelines from Bamboo.The same OAuth credentials are working for Non Prod and Prod.
I want to create a seperate Bamboo job for Non prod and Prod. So that i can have restrictive access to Prod. But the same OAuth credentials are able to set environment variables for Prod, Non Prod as well.
I don't see any way in Developer Console to control access to these OAuth credentials to work only for Non Prod and work only for Prod like that.
I guess you would have Cloud Manager API bound to this credential, like below:
Can you try removing the "Business Owner - Cloud Service" from the Product profile and see if you can still access PROD?
Correct Answer:
Open the AEM Cloud Service Developer Console by accessing the URL provided by your AEM Cloud Service environment.
Log in to the Developer Console using your Adobe ID credentials.
Once logged in, navigate to the "API Credentials" section or a similar section that allows you to manage API credentials.
In the API Credentials section, you should see a list of existing credentials or an option to create new credentials. Locate the credentials for which you want to assign a non-prod environment profile.
Edit the specific credentials you want to assign a non-prod environment profile to.
Look for an option or field that allows you to specify the environment profile for the credentials. It might be labeled as "Environment Profile" or similar.
Select the non-prod environment profile from the available options. The exact names and options will depend on your AEM Cloud Service configuration.
Save or update the credentials to apply the changes.
By assigning the non-prod environment profile to the API credentials, you are specifying that these credentials are intended for non-production environments, such as development or testing environments. This can help differentiate and manage credentials specifically for non-prod environments within the AEM Cloud Service Developer Console.
Views
Likes
Replies
Views
Likes
Replies