Showing posts with label security. Show all posts
Showing posts with label security. Show all posts

Wednesday, May 5, 2010

The Case Of The Pesky Window and Security

Maybe I am kidding myself when I think that everyone has been there. You define security in GP 10.0 (or GP 2010 for that matter), and it seems so simple. For example, the client wants to limit access to payroll data. So you use the standard roles, and you take away the Payroll Clerk role from all of them. All good right? So you test by logging in as the user, and sure enough you still see a variety of Payroll windows. Argh.

The Payroll Clerk role definitely takes care of Payroll transactions and cards, but not setup, utilities, routines, reports, Smartlist, or inquiries. Ugh. So you go hunting, and you find that the Accounting Manager role also has a variety of payroll related windows. So you adjust to remove those tasks and/or role from the users. All good right?

Not so fast, upon logging in you find that there is one stubborn remainder...Inquiry>>Payroll>>Check History. Blah. So you review the roles one more time, nothing obvious is popping out at you. What to do?

Well, there is actually a pretty fabulous KnowledgeBase FAQ on security. You will need access to PartnerSource to access it. The FAQ contains a section on security resource descriptions. To populate the tables involved, you need to complete the following steps per the FAQ:
  1. Click Microsoft Dynamics GP, point to Maintenance, and then click Clear Data to open the Clear Data window.
  2. On the Display menu, click Physical.
  3. In the Series list, click System.
  4. In the Tables pane, click the Security Resource Descriptions table, and then click Insert.
  5. Click OK.
  6. Click Yes.
  7. In the Report Destination window, select the Screen check box, and then click OK to send the report to the screen.
  8. Close the report.
Once you have completed the steps above, you can run the following script in SQL Server Management Studio to locate the Security Roles and Tasks associated with a particular window. Note the Display Name placeholder in the last part of the script, you need to substitute the display name of the window (the name that appears across the top of the window in Microsoft Dynamics GP).

SELECT ISNULL(A.SECURITYROLEID,'') AS SECURITYROLEID, ISNULL(M.SECURITYROLENAME,'') AS SECURITYROLENAME, --ISNULL(M.SECURITYROLEDESC,'') AS SECURITYROLEDESC, ISNULL(O.SECURITYTASKID,'') AS SECURITYTASKID, ISNULL(T.SECURITYTASKNAME,'') AS SECURITYTASKNAME, --ISNULL(T.SECURITYTASKDESC,'') AS SECURITYTASKDESC, R.PRODNAME, R.TYPESTR, R.DSPLNAME, R.RESTECHNAME, R.DICTID, R.SECRESTYPE, R.SECURITYIDFROM DYNAMICS.dbo.SY09400 RFULL JOIN DYNAMICS.dbo.SY10700 O ON R.DICTID = O.DICTID AND O.SECRESTYPE = R.SECRESTYPE AND O.SECURITYID = R.SECURITYIDFULL JOIN DYNAMICS.dbo.SY09000 T ON T.SECURITYTASKID = O.SECURITYTASKIDFULL JOIN DYNAMICS.dbo.SY10600 A ON A.SECURITYTASKID = T.SECURITYTASKIDFULL JOIN DYNAMICS.dbo.SY09100 M ON M.SECURITYROLEID = A.SECURITYROLEIDWHERE R.DSPLNAME = ''

So, so, so easy! I ran the script for the display name 'Payroll Check Inquiry' and received a list back of a handful of GL inquiry tasks that included the Payroll Check Inquiry window. Initially my reaction was 'Why would GL inquiry tasks include Payroll Check Inquiry?' But the more I thought about it, it makes sense from a drillback perspective. Just not from a business perspective for this particular client who does not want (even GL level users) to be able to view individual payroll check information. So, with the results of the script, I was able to eliminate those tasks for the appropriate users. Then I tested a final time, and was happy to report no payroll windows when I logged in!

I know, I know, I could avoid this by defining my own roles (and perhaps tasks), but in a simple situation like that I wanted to avoid the ground up approach if possible. And the script above is just one way to troubleshoot security when you are using and/or modifying the standard roles (or even custom roles you create).

On a side note, as I was working on this issue in GP 10.0 this week, I already was missing the functionality in GP2010 that allows you to copy role assignments from user to user, and the view filters on the security tasks and roles windows to display only selected. Funny how quickly I become attached to new functionality :)

Friday, February 5, 2010

Tracking down a GP 10 security task that is granting unwanted access to a window

I don't spend a whole lot of time in GP 10 security. I appreciate the design of the new security model, but I find configuring the security roles and tasks tedious, so I'm thankful I don't have to deal with it often.

GP 2010 does have some enhancements that will make configuring GP security easier, but for those still on GP 10, you are limited in your ability to research certain security settings.

I recently fielded a question about GP 10 security where the user was looking to remove access to specific SmartLists, but he was unable to determine which security Task in his Role was granting the access. He had unchecked all of the tasks that seemed obvious, but the SmartList was still visible to the user.

After poking around, I saw that the SmartLists were not assigned via separate, discrete Tasks--they were assigned to Tasks that provided access to other types of objects.

Below is one approach to figure out which security Tasks grant access to specific GP objects. In my example, I'm trying to figure out which security Tasks provide access to the Accounts and Multidimensional Analysis SmartLists, but you can use the same technique to track down almost any other GP object.

There may be other ways to figure this out, but this is what I came up with, which was quick and simple.

1. Create a new empty security Task (I called mine "1TEST")
2. Assign it to category Financial
3. For Product, select SmartList
4. For Type, select SmartList Objects
5. For Series, select SmartList Objects
6. Check only the Accounts and Multidimensional Analysis checkboxes
7. Save the Task

Run this SQL statement against the "Security Assignment Task Operations" table:

SELECT * FROM DYNAMICS..SY10700 WHERE SECURITYTASKID = '1TEST'

This will list the security IDs for those specific SmartLists. In my TWO database, they are 1 (Accounts) and 14 (Multidimensional), with a security resource type = 1000 (presumably SmartLists).

Now, query the security task table again to see what other tasks are granting access to those two SmartLists:

SELECT * FROM DYNAMICS..SY10700 WHERE SECRESTYPE = 1000 AND SECURITYID IN (1, 14)

In my TWO database, that shows me that the following Tasks are providing access to those SmartLists:

1. CARD_0101 (Accounts)
2. CARD_0102 (Accounts and Multidimensional)
3. INQ_FIN_001 (Accounts)
4. INQ_FIN_002 (Accounts and Multidimensional)


This quicky tells me all of the Tasks that provide access to those SmartLists, so now I can go back to my Role and determine how I want to remove access.

I could uncheck all four of the Tasks, which will do the trick, but it may also remove access to windows that the user should be able to access.

Another approach would be to modify those Tasks to remove access to the two SmartLists. This would also work, but any other users that rely on those Tasks to view the Accounts and Multidimensional SmartLists would lose access as well. In that case you can create a new tasks that gives access to those SmartLists, and add that task to a new or existing role for users that need access.

Clear as mud?

Tuesday, June 23, 2009

White Papers Aplenty

Sometimes it feels like I go through phases where white papers just seem really applicable to issues that come up both within my company and with customers. Having just been through one of these phases, I thought I would share some of my favorites...


Microsoft Dynamics GP and SQL Server 2008
Partners: https://mbs.microsoft.com/partnersource/documentation/whitepapers/mdgpsqlwhitepaper.htm?printpage=false
Customers: https://mbs.microsoft.com/customersource/documentation/whitepapers/mdgpsqlwhitepaper.htm?printpage=false
Interesting whitepaper on the benefits of compression with SQL Server 2008, including benchmarking results on performance.


Choosing a Development Tool for Microsoft Dynamics GP 10
Partners: https://mbs.microsoft.com/partnersource/documentation/whitepapers/gp10_toolswhitepaper.htm?printpage=false
Customers: https://mbs.microsoft.com/customersource/documentation/whitepapers/gp10_toolswhitepaper.htm?printpage=false
This is a great overview of the available development tools, for both developers and application consultants to familiarize themselves with the licensing costs as well as the skills needed to successfully use them, and the capabilities of each tool.


Planning for Security in GP 10
Partners: https://mbs.microsoft.com/partnersource/documentation/whitepapers/msdygp10_securityplanwp.htm?printpage=false
Customers: https://mbs.microsoft.com/customersource/documentation/whitepapers/msdygp10_securityplanwp.htm?printpage=false
This serves as a starting point for security discussions, and it looks at security in a holistic way (not just within the Dynamics client specifically). It reminds me that security is more than roles and tasks.

Deploying Microsoft Dynamics GP 10 in a Multinational Environment
Partners: https://mbs.microsoft.com/partnersource/documentation/whitepapers/deployinggpmultinationalenvironment.htm?printpage=false
Customers: I could not find this on CustomerSource, but please feel free to post on this blog if you cannot access.
This is an older white paper, but I always re-read it before embarking on a multinational implementation. It just helps remind me of the installation considerations and pitfalls of multiple countries, localization requirements, and languages.


Strategies for Multi-Entity Environments in Microsoft Dynamics GP 10
Partner: https://mbs.microsoft.com/partnersource/documentation/whitepapers/strategiesmultientityenvironmentsgp10.htm?printpage=false
Customer: https://mbs.microsoft.com/customersource/documentation/whitepapers/strategiesmultientityenvironmentsgp10.htm?printpage=false
This is another older white paper, but it again reminds me of the considerations of one database -vs- many. I have a worksheet I have developed to assist with the assessment, but this document definitely helped me refine it further.

Achieving Compliance Objectives in Microsoft Dynamics GP 10

Partner: https://mbs.microsoft.com/partnersource/documentation/whitepapers/helpachievecomplianceobjectivesgp.htm?printpage=false

Customer: https://mbs.microsoft.com/customersource/support/documentation/whitepapers/msdygp_whitepaper_achievecomplianceobjectives.htm?printpage=false

This white paper presents a general view of compliance, how to begin the process, and some aspects to review. It is a great starting point for those that are new to compliance requirements, and need some assistance in where to begin.

Please share your favorite white papers, and I will update the post. You can find many more white papers through Deployment>>White Papers on PartnerSource, or through Documentation>>White Papers on CustomerSource :)