Introduction

Enterprise resource planning (ERP) systems such as Dynamics NAV need a built-in security model to make sure that the appropriate people have access to the appropriate information. NAV supports four forms of user authentication: Windows, Username, NavUserPassword, and ACS. Each login has assigned roles, which in turn have permissions, which the system checks every time data is accessed or an object is run.

NAV security is somewhat limited and difficult to maintain. However, as system-security data is stored in tables of the NAV database, we can write a custom code to handle permissions in any way we like. We can even make calls to the Active Directory to examine user groups and other Windows properties. As you will see in this chapter, the boundaries of NAV security are limitless, but there will be a large amount of work involved for certain tasks.