How to: Test the Role-based Security Configurations under AOT Security
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
This topic explains how you can test the security configurations that are specified under the Security node in the AOT.
The user who installs the product is part of the SYSADMIN role. Users in the SYSADMIN role can access all tables and other resources regardless of the security settings. Therefore these users cannot test the security configurations. To test with limited permissions you will have to add application users.
Roles for Testing
To implement and test security, you must act as a user in the roles of a developer, a system administrator, and an application user. The tasks for each user during testing are described in the following table.
Role |
Description |
|---|---|
Developer |
The developer has no tasks to perform during testing, unless an error is found. The developer configures the desired security before the test phase starts. |
System administrator |
During testing the system administrator assigns an application user to the test roles. |
Application user |
The application user is a user who has limited permissions for accessing securable objects, such as tables, forms, and menu items. |
Use the System as an Application User
As a system administrator, you must create user accounts to use for testing. Before you can add a user to the list of Microsoft Dynamics AX users, the user must be listed in Active Directory in Microsoft Windows. For more information, see Work with users from Active Directory.
After making sure that an application user exists in Active Directory in Microsoft Windows, you must add an application user to Microsoft Dynamics AX. For more information, see Create new users in Microsoft Dynamics AX.
After adding the application user to Microsoft Dynamics AX, you must assign it to the application user test role.
The following steps describe how you can run the Microsoft Dynamics AX client as an application user.
Open a Command Prompt window on the computer where you installed your Microsoft Dynamics AX system.
Use the runas command to allow an application user to run the AX32.exe client application with permissions that differ from those of the current Windows user. Type the following code into the Command Prompt window, and then press the Enter key:
runas /user:<ApplicationUserDomain>\<ApplicationUser> Cmd.exe
Execution of the runas code line opens a new Command Prompt window. The new window has the limited security permissions of the application user.
When you are prompted, type the password of the application user.
In the new window type Ax32.exe to run the client as the application user. Ax32.exe client program should be in the command path of your test system.
See also
Security Permissions for Securable Objects in the AOT
Create new users in Microsoft Dynamics AX
Announcements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. Get your copy at the MS Press Store.