![]() Two questions: Why did we need to set the permissions for the Menu Widget at both the Content Type level and the Widget instance level. Otherwise it overrides what we already set.Īt this point, the solution works perfectly. At the content item level, we also had to set the following permissions: Widget > Specific Menu Widget > Enable content item access control Disable this (i.e. Content Definition > Menu Widget > Parts Content Permissions Anonymous Authenticated To fix that we added the Content Permission part to the Menu Widget and adjusted the settings. The problem at this point was that revoking View all/own content for the anonymous role meant that this role could not see the Menu Widget on the front end. Guest users can only send solicited packages. Files from those who do not hold a CAC cannot be sent unilaterally, said Holder. ![]() Further, we kept the default settings for the authenticated role, because the defaults include View all/own content, include the new Secure Page content type that we created. In addition to package level encryption, DOD SAFE is also improving security by requiring authenticated Common Access Card (CAC) users, who are the main user base of DoD SAFE, to initiate all file transfers. We revoked View all/own content for the anonymous role, and then explicitly re-granted View permission to this role for both pages and projections we did not re-grant View permission for secure pages. Users > Roles (View & Access Permissions) Anonymous Authenticated What we are wondering is, "is there a better way?" and "What's up with needing to set permissions both at the level of the content type and the widget instance for the menu widget?"įirst we created a new Secure Page content type. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |