AIO rde cli issue - not able to run install command to deploy pkgs/file

[nishisharma]

I am getting below error while running "aio aem:rde:install ....." command

I am able to login to rde environment and developer console separately on the browser but not able to push packages.

Any quick help on this?

Any specific access is required to run this command?

[sravs]

@nishisharma please make sure you are executing "aio login" before executing the above command. A browser window should open, asking you to sign in with your Adobe ID. If the window did not automatically open, you can also copy paste the URL printed in command prompt to your browser to log in. This will make sure you're logged Adobe I/O.

Please refer https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aio-rde-cli-login-issue/m-...

[HrishikeshKa]

Hi @nishisharma ,

I would suggest to get your access checked for 403 Forbidden Error.

It might just be possible that you are using a different account to access the CLI. This sometimes can happen if you are using multiple IDs which are associated with SSO for Adobe applications.

If you want to refresh simply try the below commands -

aio logout

aio login

The browser sign in window for CLI should appear.

Thanks!

[nishisharma]

I have tried all above suggested options...but no luck

[sravs]

@nishisharma , check your access for the enivronment which you are trying to push the changes. From your logs it's clearly mentioned that 'Access denied' for program id 123713

[nishisharma]

That's the question actually. I am able to access RDE env separately from bowser and can do configurations using UI. What exactly is restricting me to push code to RDE via aio-cli?

[sravs]

@nishisharma , can you try checking access by executing "aio aem:rde:status"command

Refer https://medium.com/@toimrank/adobe-cloud-manager-rapid-development-environments-rdes-7a7a36c50b9

https://techrevel.blog/2024/02/14/aem-rde/#resolutions

[nishisharma]

Same error while running "aio aem:rde:status"command:

[sravs · Accepted solution]

Check the permissions mentioned here https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/adobe-i-o-api-call-access-...

[kautuk_sahni]

@nishisharma Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.