Openid is not directly supported but can be used via community projects as per [1] You can check [2] for sample implementation under the communities project. [1] https://experienceleague.adobe.com/docs/experience-manager-learn/foundation/authentication/authentication-support-article-understand.html?...
I tried to run it on the author on cloud service and it worked... The configurations for which we need to get into the system console can be done via OSGi so should not be a problem... For publisher just need to make sure /apps/groovyconsole.html accessible via dispatcher and the validator doesn't c...
You cannot run AEM without a proper license in place. That said, you can reach out to the team[1] for demo/consultation Or a POC. [1] https://business.adobe.com/ca/request-consultation/experience-cloud.html
Bootdelegation changes are only required if you are using Java 11. Check the following: - You are using the latest code at : https://github.com/adobe/aem-guides-wknd- The build was successful and packages were installed without any issues on the AEM instance- When building the code, use the "classic...
The forbidden(403) error means the Publish IP is not allowed to make flush requests to the dispatcher. Basically, the dispatcher checks all the allowedclients and if publish IP is not there, It does not allow any requests from that IP to be run on the dispatcher. Although it seems like a user permis...
The alias is only generated/needed when setting up SAML and it should be a one-time activity. So, if the underlying certificate is not changing, you can use "config.author" for author SAML config and "config.publish" for publish SAML configuration and the alias will be applied as per the runmode. If...
Error[1] means something wrong with your datastore. Either the user running AEM does not have permissions to the crx-quickstart/repository/datastore folder or something else going on with the datastore. [1] error: java.lang.RuntimeException: Error occurred while obtaining InputStream for blobId [3e1...
If the issue is not reproducible on the WKND site, I highly doubt it's an issue with the core AEM code and the issue might be related to the Sling model Or other backend custom code that gets invoked during the component deletion. That said, If you are able to reproduce it without any custom code, I...