Adobe support said there's no reason it shouldn't work as long as the policy is unconfined enough, but my recollection from the ticket is that Adobe does not provide help configuring SELinux.
One thing you can do on RHEL if running into issues:
sealert -a /var/log/audit/audit.log
This command should provide the additional commands required to allow whatever might be required for AEM. You may need to run it many times to get a policy that is permissive enough for AEM.
You should be careful not to permit anything that might be reported via sealert that is not required by AEM.
Thanks for the info, I had seen this too. I'm pretty sure we're not running AEM Dynamic Media Add-on. In this case I wonder if there are any other things that might break? In testing, I think we've been able to get a policy in place that allows us to start and stop the author and publish services successfully but our SAML2 login seems to have suddenly stopped working with error: Invalid SAML Token. This is possibly unrelated but will take some debugging to determine.
Adobe support said there's no reason it shouldn't work as long as the policy is unconfined enough, but my recollection from the ticket is that Adobe does not provide help configuring SELinux.
One thing you can do on RHEL if running into issues:
sealert -a /var/log/audit/audit.log
This command should provide the additional commands required to allow whatever might be required for AEM. You may need to run it many times to get a policy that is permissive enough for AEM.
You should be careful not to permit anything that might be reported via sealert that is not required by AEM.
