Best Practices for Configuration and Security Keys [AX 2012]

Updated: March 11, 2014

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Configuration keys determine which features are turned on during the installation.

NoteNote

Security keys are obsolete in Microsoft Dynamics AX 2012 and only exist to use for reference during a code upgrade. There is a new security framework, which is called role-based security. For more information on the new security framework, see Role-based Security in the AOT for Developers.

Configuration keys should be defined so that the installation can be set up with only the features needed for each particular installation. By disabling configuration keys, administrators can reduce the potential surface of attack, thereby helping to increase the security of their Microsoft Dynamics AX installation.

Configuration keys are often arranged in hierarchies of functionality, mirroring the hierarchies of functionality in the application.

Property

Rules

 Name

Follow the standard Naming Conventions.

If you attempt to create a configuration key by using a name that has already been used for a configuration key in Microsoft Dynamics AX, an error will occur. Error icon


Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.

Community Additions

ADD
Show: