STEP 1: CREATE A NEW USER IN ACTIVE DIRECTORY
This is beyond the scope of this article, mostly because I just contacted our system admin and he did it for me. I did request that the name be WebSiteUser.
STEP 2: CREATE A NEW APP POOL IN IIS
Open Internet Information Services (IIS) Manager. In the Connections (left) panel select Application Pools. In the Actions (right) panel click Add Application Pool. Add a name and click ok.
In the Center panel your new pool should be highlighted. Notice that the Identity column shows ApplicationPoolIdentity. In the Actions (right) panel click Advanced Settings. Scroll down to Identity. Click on the ellipses. Select Custom Account, and Set. Enter “domain\” and the newly created user and credentials from the previous step.
STEP 3: CHANGE THE APP POOL OF YOUR APP
In the Connections (left) panel click once on your app. In the Actions (right) panel click Basic Settings. Click Select and change the Application pool to the one you just created in step 2.
STEP 4: ADD THE USER TO GP
Open Dynamics Security Console. In Console Root (left) panel expand Microsoft Dynamics Security and then expand Microsoft Dynamics GP Web Services. Select Role Assignments. You can get to the Add screen two different ways, right click Role Assignments or in the Actions (right) panel click Add. Select a Role (I used Superuser) and click the Add Windows User. Enter “domain\” and the newly created user. Click Check Names, the system will fill in the AD user info. Click Ok. Back on the Add Role Assignment dialog screen make sure you select a company to apply this user to.
NOTE **
If you have a factory standard installation of GP please note your changes may not take effect immediately. Per the GP Web Service Installation and Administration Guide the security settings are cached and only updated every 20 minutes.
FINAL STEP: TEST APP
Open a browser and navigate to your application. You should now be able to reach the GP data.