as above. some information/notes: I checked the IDP metadata that was given to me by our Okta team I checked OSGI config I checked author dispatcher config I checked SAML response (using SAML tracer browser plugin) I can successfully login to Okta I read this troubleshooting guide in case I miss som...

problem: I've been using VLT to sync the content but quite often (and normally present in large folders), VLT will encounter an error and will throw an exception. setup: - The 2 AEM environment have separate servers for author, publisher and dispatcher. - The 2 AEM environments are hosted by differe...

what if the 2 AEM instances are in separate servers and there's no way to share/mount the storage that contains the crx-quickstart? Thanks again

scenario:I have 2 AEM environments: pre-prod and prod pre-prod = environment which contains all the latest code/configuration changes (this includes feature requests and bug fixes BUT not the latest content). prod = currently running environment that's available to the public. (Not so latest code/co...

I edited my original reply.I tried the following: browsed http://www.my-host.com/system/health and nothing showed up in /var/log/httpd/dispatcher.log I ran this curl -vvv -k https://localhost/system/health and got this reply. I also got nothing in the logs. 404 Not Found Not Found The requested UR...

I will check the log level. I think it's already using "warn". I already have a specific rule for /system/health and it's not working. I'm only did the global allow everything once the specific rule is not working.

might be explained with an example: When I accessed the publisher health check directly, it is working fine. Sample URL: 10.0.0.1:4503/system/sling/monitoring/mbeans/org/apache/sling/healthcheck/HealthCheck/inactiveBundles.json When I try the same path but via dispatcher (sample URL: my-host.com/sys...

as above. I think there's not much need to worry about frontend. it's the backend that I'm more concerned with. I searched the net and came across 1 discussion where the only thing that needs to be changed is upgrading (using a newer version that's been compiled or arm) a mvn "plugin". Thank you!

scenario: There is a public page that's behind a login. We're not using the built-in SAML authentication ("Adobe Granite SAML 2.0 Authentication Handler" - com.adobe.granite.auth.saml.SamlAuthenticationHandler) that's provided by AEM publisher. --- I had a look at the cookies and login-token cookie ...

I've seen that but it seems the consulting firm who put the "protected" pages in place decided to bypass the built-in SAML functionality and implemented their own.