I was trying to follow the official documentation for creating SAML auth configurations with the below KB article. https://docs.adobe.com/content/help/en/experience-manager-65/administering/security/saml-2-0-authenticationhandler.htmldemo url : https://helpx.adobe.com/experience-manager/kb/simple-sa...

thanks for the reply, even after adding the method to apache sling referrer filter, we are still facing the issue. it's strange that the local host is giving 401 for me as well in publish even without adding any configurations, really confused what should be next steps here. @arunpatidar

Hi @Jörg_Hoh, we also know that this has to be blocked at apache level, but there is a security vulnerability that AEM HTTP OPTIONS opened, so we have to fix the issue

Even after adding OPTIONS method to filter methods in both Adobe Granite CSRF filter and Apache sling referrer filter, the CURL requests are still responding with 200 response. curl -i -X OPTIONS http://<host>:<port>/content/*****/en/****/home.htmlHTTP/1.1 200 OKDate: Thu, 22 Oct 2020 17:42:30 GMTX-...

Hi @Vijayalakshmi S, I tried to get the bundle status using the same user name and password and i'm able to get the json response

Hi @Vijayalakshmi_S, If we are trying to access the publish instance felix console, it redirects to login page and it is not allowing to login into AEM

Hi @Vijayalakshmi_S, we generally don't follow the document process, we genrally stop the server.copy crx-quickstart from one path to another path and datastore from one path to another path, update the blob datastore config (org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore.config) to ...

we run aem 6.3.2.1 server on segmentstore, we copied the complete segement store, datastore into different paths updated the configurations and deleted the sling id and changed the port  number and started the server on the same host. once the server is started, not able to login even with root admi...

even with dispatcher infront of the AEM instance, they want to make sure AEM is running on https section

thanks for the quick response, can we run AEM only on https port and not accessible on http? Will ther be any impact in using the https port in the dispatcher configuration?