Ticket T600540
Visible to All Users
Duplicate

We have closed this ticket because another page addresses its subject:

Permission not worked in 17.2.5

Questions on the new permissions processing mechanism

created 7 years ago

[DevExpress Support Team: CLONED FROM T559861: Security permissions processing mechanism optimization and other important changes in XAF v17.2+]
In 17.2.5, why is the new permission not available when it added by the Updater class?
If you are new to your own permissions is no problem, but in the updater of this class automatically new permissions will not take effect.

Comments (2)
Dennis Garavsky (DevExpress) 7 years ago

    Hello He,

    Your initial setup, the new code you wrote in the ModuleUpdater class and the "new permission" you are referring to as unavailable are unclear to us to comment on this. Would you please attach a small sample and screenshots clarifying this?

    For now, I can only suggest you check the following things in your project:

    1. Make sure that you are using the new permission Allow/Deny policy with its PermissionPolicyXXX APIs. If this is not the case, follow How to upgrade an existing project to the Allow/Deny permission policy (migrate to PermissionPolicyUser and PermissionPolicyRole)
    2. Debug your app and check that the following properties are set to expected values, e.g. inspect them during Controller activation:
      SecurityStrategy.AssociationPermissionsModeSecurityStrategy.UseOptimizedPermissionRequestProcessor  and SecurityStrategy.RolesMergingMode
    Dennis Garavsky (DevExpress) 7 years ago

      I have found your related ticket: Permission not worked in 17.2.5. Let's continue discussing this behavior there. Thanks.

      Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.

      Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.