@NitroHazeDev That is correct. This package is only for the publish server(s) as that is the only point (as OOTB) that interacts with vanity URLs. You could technically enable it for the author server too if you have it running via the dispatcher, but it would not provide any real benefits. To check...

@karlschaenzer This is likely due to the OOTB XSS configuration which restricts the URLs allowed in an <iframe> element. What you would need to do is overlay the existing configuration as documented at the below link. Within the configuration update the iframesrc property regex to include your URL. ...

@raushan123 If I am understanding correctly you want your second rule to be ignored when the request URI begins with /content/test/de/de/. RewriteRule ^/content/we-retail/de/de/(.*.html)$ https://%{SERVER_NAME}/$1 [NE,R=301,L]RewriteCond %{REQUEST_URI} !^/content/test/de/de/RewriteCond %{REQUEST_URI...

@this-that-the-otter I'm pretty sure I understand the desired outcome so let's break things down. You only require SAML for a non-default author URL, i.e /fooYou want the standard AEM authentication to remain for / If that is correct then what you can do is this, keep the IdP Consumer URL as https:/...

@NitroHazeDev The simplest thing to try would be to download and install the vanityurls-components package in your publish environment. The latest archetypes come with this component enabled by default in the dispatcher configuration which is likely the cause of the log messages.   If you find you d...