Authentication to aio app builder from custom mcp | Community
Skip to main content
B
BhavaniBharani
Level 4
October 23, 2024

Authentication to aio app builder from custom mcp

  • October 23, 2024
  • 1 reply
  • 1060 views

Hi,

 

I am currently working on assets with metadata migration task using the aio app builder. Calling the aio app builder code from custom MCP in AEM. When trying to make a call to app builder worker from custom mcp i am getting 401 authorization header is missing. I would like to know how to solve this issue. As it is expecting aio login token and org id from custom mcp also the login token will get refreshed every 24hrs, do we need to write a logic to generate the login token by passing the client credentials? Please let me know if anyone aware of this.

 

 

Thanks,

Bhavani Bharanidharan

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

martin_ecx_io
Community Advisor and Adobe Champion
martin_ecx_ioCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
October 23, 2024

To make use of the standard aio endpoint authentication you would likely need to implement the full oauth token generation process in your codebase, taking your client key etc and using the token API to convert this into a token.  You could potentially cache this for a period of time to avoid every call to the service needing to generate a new token.

 

An alternative approach would be to look at disabling the "adobe auth" option in the adobe io worker, then implement your own authentication, eg pre-shared key etc.  This potentially simplifies the flow, but you need to consider the security impact of doing this as the adobe io API endpoint is effectively public.

 

You can disable the out of the box auth requirement for the endpoint by updating the manifest.yml

annotations: require-adobe-auth: true

 

 

    B
    BhavaniBharaniAuthor
    Level 4
    October 24, 2024

    Hi @martin_ecx_io ,

     

    Thanks for your suggestion. I have added the logic to create a access token using the client credentials. Now I can able to see that i am not getting 401 unauthorised error, but getting 204(No content) status code. When i check the logs in app builder, i am not able to see any request is triggered at that time. 

     

    Workaround: When i hit the same app builder url from postman, i am getting 204(No Content) status code. 

    My doubt, i do have some logs added at starting of the execution. Even that is not getting prinited in the aio runtime activation logs.Do you have any idea about this? 

     

     

    Thanks in advance!

     

    Regards,

    Bhavani Bharanidharan

      Terms & ConditionsAccessibility statement

      Loading footer...