hey @aanchal-sikka can you share more insights on how i can disable the name field.from what i can see, when i try to access the new content fragment screens, it takes me to some cloud based app.it looks like the application is hosted independently.
Hello Vikram I'm got a similar use case herehttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/enforce-naming-convention-for-content-fragment-in-aemaacs/td-p/625052 How can i use JcrUtil to enforce valid naming convention before the content fragment is persisted ? Which java f...
@gmalagondla @sanith I'm in the same boat. Please let me know if you receive any update from them ?My JWT token were nearing expiry and we decided to migrate to OAuth instead of refreshing the token. Looks like we can't go back to using JWT tokens once the migration has happened Affecting our build...
Thanks for the reply. I'm not sure about the source of your info but MDN says Only a single origin can be specified. If the server supports clients from multiple origins, it must return the origin for the specific client making the request.I have tried adding a list to Access-Control-Allow-Origin an...
@arunpatidar Access-Control-Allow-Origin unfortunately accepts only single value. I'm trying to stay away from wild card * due to security recommendations.
Thanks for your time @SantoshSai
I tried this and it is still leading to unresolved dependencies wrt AWS SDK.
I have used several third party dependencies and faced no issues with them, it is just AWS that is causing this issue.
Please let me know if you can think of any other resolution.