With AEM 6.4 SP8, Adobe introduced restriction that only members of the AEM administrator group could publish to the Brand Portal. This request is to align publishing permission for the Brand Portal with the standard replicate ACL.
Use-case:
An AEM Assets user--i.e. a designer or a marketer--completes work on an asset and would like to publish the asset to the Brand Portal. The administrator for AEM would like to be able to grant that user the permission to publish their assets to the Brand Portal without making them an administrator (and granting many permissions which are inappropriate for their role).
Current/Experienced Behavior:
Only members of the AEM administrators group can publish to the Brand Portal
Improved/Expected Behavior:
Users with replicate permissions on the asset or folder can publish to the Brand Portal
Environment Details (AEM version/service pack, any other specifics if applicable):
This is applicable since AEM 6.4 SP8 through AEM 6.5 SP11 as well as the current build of AEMaaCS
Not trying to discredit your need at all (definitely nor discredit the desire to make it behave more standard) but as a workaround are you having your non-admins publish this content via a workflow instead? I think that's working for us.
@timothygrimes - Good question. Yes, we could do this via workflow (although to my knowledge there is no OTB workflow step to publish to the Brand Portal in specific, so we'd have to write a custom workflow step), but it seems like a poor use of our clients' customization budget to address a functionality that should be in the product. Also, while I won't say we've never built customizations to workaround to product-level security constraints, it's not my favorite approach due to the potential to open up a security hole. If Adobe doesn't address via the product roadmap, we'll likely do as you suggest.
@FreedomMarketin Yea, we did have to setup a custom workflow but not a custom workflow step. We just use the com.adobe.acs.commons.workflow.process.impl.BrandPortalSyncProcess process step. Note, it's incompatible with AEMaaCS.
Thanks for proposing the idea! I see this has already been reported to product team via internal request CQ-4339672.
The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Thanks for the update. Since we posted this, we did find a way to make this functionality available via security updates rather than customization. We have only verified this functionality in 6.5. The security adjustments may not be possible in AEMaaCS.
