Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Adobe Experience Manager Forms 6.5 on JEE (Document Security)

jaemyoung_r1184
Level 1
Level 1

 

Error in setting Policy (Print, Modify, Copy) in adminui.
The checked setting value is not reflected.

Install version : 6.5.0.20200526.1.938669

 

 

dolhead@northstar.co.kr_inline_img_FBA86F582B2B4578A54039A645B18B6A.jpg

 

============================

 

dolhead@northstar.co.kr_inline_img_9A91A5A4C4C84D09825814FD50C24D36.jpg

 

9 Replies
Mayank_Gandhi
Community Advisor
Community Advisor

@jaemyoung_r1184  Please check the roles assigned to the user trying to update the policy.

Kosta_Prokopiu1
Employee
Employee

See here for AEM Forms Permissions, look at the Rights Management permissions. The user must either be Super Administrator, or Rights Management Policy Set Administrator or Rights Management Super Administrator or must have permissions as listed further down on that page.

https://experienceleague.adobe.com/docs/experience-manager-64/forms/administrator-help/setup-organiz...

jaemyoung_r1184
Level 1
Level 1

The operation was performed with the administrator account.

And in 6.3 Version, it worked well in the same way.

Kosta_Prokopiu1
Employee
Employee

It seems that this behavior has been experienced by others. Please open a case with Adobe Support.

PulkitJain
Employee
Employee

@jaemyoung_r1184 

This issue (along with multiple others under the Document security module) has been fixed with the latest AEM Forms 6.5.8.0. I have checked my in-house latest patched set-up, don't see these error msgs.

 

 

Release notes: https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/service-pack/sp-release-... ; check bug details under "Document Security"

Mayank_Gandhi
Community Advisor
Community Advisor

@jaemyoung_r1184  There was a strut upgrade in 6.5.7 and that seems to be causing an issue with the Policy screen. Hopefully, patching will help if this is fixed already else you will have to raise a bug.