Download presentation
Presentation is loading. Please wait.
Published byDwain Black Modified over 8 years ago
1
www.hso.com Understanding the Dynamics AX2012 Security Model 4/14/2014 AXUG User Group Meeting
2
Copyright © HSO Presenters: Sandra Larrea – VP Professional Services Alan Linhart – Solution Architect
3
Copyright © HSO Agenda Welcome Show of Hands Security overview Demo General Tips and Best Practices Questions
4
Copyright © HSO Show of Hands Dynamics AX version 4.0 2009 2012 2012 R2 Security Administrators Developers Upgrading
5
Copyright © HSO AX2012 Security Model (Role-based) Process cycles Tables and fields Duties SSRS reports Privileges Service operations Roles User interface elements Securable objects
6
Copyright © HSO AX2012 Security Model Template Roles, Duties and Privileges are delivered ‘out of the box’ Roles are system-wide Assign user access by attaching to an organization This should be done from the beginning not at UAT
7
Copyright © HSO AX2012 Security Model Roles >Assign to users; may contain sub roles, duties, privileges, and permissions Process Cycle>Business process; grouping of duties Duty>part of a business process; SOD Privileges>Contain permissions Permissions>Group of securable objects and functions for a specific function
8
Copyright © HSO AX2012 Security Model Record level security is still available -Deprecated in a future release -Replaced by eXtensible Data Security (XDS) Setup users via Active Directory Groups No direct upgrade path from previous versions of AX Limited security reports still
9
Copyright © HSO Segregation of duties (SOD tool) Preventative control Analysis performed at duty level Limitations - Security overrides - AD group inheritance
10
Copyright © HSO Tools Security Upgrade Advisor Tool Security Development Tool for Microsoft Dynamics AX 2012 http://informationsource.dynamics.com
11
Copyright © HSO AX2012 R2 Partition concept (Silos not sharing data) - Uses same building blocks of Roles, Duties, and Privileges - Meta data are still shared - Each partition has it’s own list of authorized users - User/Role assignments are per partition
12
Copyright © HSO DEMO Create AX user/Assign Roles Assign Users to Roles Manage Roles/Duties/Privileges GUI to AOT tracing
13
Copyright © HSO Documentation Role-based Security Use Patterns for Developers - http://www.microsoft.com/en-us/download/details.aspx?id=39068http://www.microsoft.com/en-us/download/details.aspx?id=39068 Developing Extensible Data Security Policies - http://www.microsoft.com/en-us/download/details.aspx?id=3110http://www.microsoft.com/en-us/download/details.aspx?id=3110 Security Roles and Licensing Whitepaper - http://download.microsoft.com/download/B/6/6/B66540B2-C8D7- 4C5C-91D5- FF6760906A7B/MSDAX2012 Security Roles Licensing Whitepaper.pdfhttp://download.microsoft.com/download/B/6/6/B66540B2-C8D7- 4C5C-91D5- FF6760906A7B/MSDAX2012 Security Roles Licensing Whitepaper.pdf - http://www.microsoft.com/download/0/3/A/03A2D4A2-47A3-45E3- 85A7-5F465E141F0F/MSDAX2012 SecurityRolesLicensing.PDFhttp://www.microsoft.com/download/0/3/A/03A2D4A2-47A3-45E3- 85A7-5F465E141F0F/MSDAX2012 SecurityRolesLicensing.PDF
14
Copyright © HSO Licensing Information Enterprise Users - Accountant, IT Manger to Warehouse Manager Functional Users - Buying Agent, CSR to Warehouse Worker Task Users - Field Service Technician Self-serve Users - External Customer/Vendor
15
Copyright © HSO Security Development Tool
16
Copyright © HSO Tips Watch the use of giving people ‘SysAdmin’ as sometimes they never have this taken off. Best to create your own roles, which will help with upgrades Must setup security if apply new code, otherwise users will not see it ‘SystemUser’ is default role when user setup, careful as it has hidden privileges Excel integration is only allowed with ‘SysAdmin’ role Duplicate roles rather than creating them from scratch
17
Copyright © HSO Best Practices Start the security up front and build this into the Project plan. Best to create your own roles, which will help with upgrades Must setup security if apply new code, otherwise users will not see it ‘SystemUser’ is default role when user setup, careful as it has hidden privileges Test security and add to a project to promote, just like code Create new menu item for customizations with two priviledges (view and maintain) Start by assigning access then remove permissions afterwards
18
Copyright © HSO Questions ????
19
www.hso.com Thank you! 04/14/2014 AXUG User Group Meeting
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.