1 / 39

Progress Dynamics™ 2.1A

Progress Dynamics™ 2.1A. Group Security. Cheryl LaBarge, Product Readiness tPC Neil Bell, Progress Dynamics Development. Agenda. Security Review Key Enhancements Guidelines Demonstration Questions and Answers. Security Review. Security Model User Types Structures Allocations

bert
Download Presentation

Progress Dynamics™ 2.1A

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Progress Dynamics™ 2.1A Group Security Cheryl LaBarge, Product Readiness tPC Neil Bell, Progress Dynamics Development

  2. Agenda • Security Review • Key Enhancements • Guidelines • Demonstration • Questions and Answers

  3. Security Review • Security Model • User Types • Structures • Allocations • Resolution of Model

  4. Security Model Revoke Scenario- Application for Subsidiary Offices with access available to the majority of application

  5. Security Model *Grant Revoke Scenario- Application for vendors to update products available to internal system for ordering

  6. Security User Types – WHO? • Users • Individuals • Option available to make profile User • User Categories • Descriptive grouping of users • *Security Groups • Automatically propagate changes • Not hierarchical • Conflicts resolved with least restrictive approach

  7. Security Structures – WHAT? • *Actions • Data Ranges • Fields • Login Companies • Default Structures • Containers • Data • Menu Items • Menu Structures Containers Data Menu Items Menu Structures

  8. Security Allocations – HOW? • Associate who may use what? • Associate users to structures • Define key parameters • Document the purpose of the association

  9. Resolving Conflict Most specific to least checking • Specific user, specific login company • Specific user, any login company • All groups, to which the user belongs • If more than one, it applies cumulative least restrictive • Allocations against all users • Within the category, • Allocation against all users within specific login company • Allocation against all users within alllogin companies

  10. Apply the Rules Model = Revoke Groups A B C 3 User Maintenance Record – Action - Folder 1 User – No restriction on the user 2

  11. Agenda • Security Review • Key Enhancements • Guidelines • Demonstration • Questions and Answers

  12. Enhancements - General • Support for group based security • Default security groups – new users linked automatically • Addition of grant model • Improved UI for security leveraging treeview interface • Security Maintenance • Security Allocations • Security Query • Security Processing

  13. Secondary Features • Conversion function – user to groups • Fully documented API

  14. Enhancements Issues • 11422 - Order of security allocations at runtime • 11237 - Consolidated groups • 11349 - Group w/out security allocations treated as consolidated group • 11311 - Assigning default groups (check the resolution) • 11346 - Overriding group restrictions at the user level • 11621 - Data ranges API uses chr(3) delimiter • 11975 - Can't set security structures below container level

  15. Agenda • Security Review • Key Enhancements • Guidelines • Demonstration • Questions and Answers

  16. Guidelines • Choose model • Identify functionality access • Consolidate groups • Plan default • Plan company • Plan user • Review model for complex overrides • Implement security model

  17. Security Demonstration • Outline scenario • Follow guidelines • Implement using product

  18. Case Study Scenario • Sporting Goods application • Typical Users • Admin – all access • Jr. Salesrep • Robert Newman • Seth Macabee • Nicole Milton • Sr. Sales Representative • Charles Oliver • All Sales • Tom Gun

  19. Choose a Model *Grant Revoke Scenario- Most user have access to application. Easiest to revoke.

  20. Replacing a Model • Backup your current security work • Backup the appropriate tables GSMFF - Fields GSMGA - Group Allocations GSMLG - Login Companies GSMSS - Security Structures GSMTO - Actions (Tokens) GSMUS - Users (and Groups) • Please note that Group Allocation and Users are not exported separately they are combined in the GSMUS export.

  21. Setting Your Security Model

  22. Identify Functionality Access • Jr Salesrep • Default group • Limited access • Balance hidden • Credit Limit and Discount read-only • Sr Salesrep • Override the default on balance read-only • All Salesrep • Combines both groups with least restrictive result

  23. Consolidate Groups JR SR Customer Info Order Entry All Sales

  24. Plan Default • Default group • Jr Salesrep • Senior level group with more access • Sr Salesrep

  25. Plan Company Default Company • Starting small • Only our default company • Major concern for hosted applications that might have multiple vendors sharing the application resources • Third Party Group for new companies SR JR All

  26. Plan User • Typical Users • Admin – all access • Jr. Salesrep • Robert Newman • Seth Macabee • Nicole Milton • Sr. Sales Representative • Charles Oliver • All Sales • Tom Gun

  27. Review For Overrides • You can remove a menu structure for an individual • Nicole Milton • Jr. salesrep • Access to Order Entry • User override • Restrict Order Entry MenuBand Menu Band Restricted

  28. User Overrides Jr Sales • Example • Seth Macabee • Jr. Salesrep group member • Balance field – Hidden • User Override • Balance field – Full Access User– Seth Macabee

  29. Establish (Maintenance) Actions Data ranges Fields Login Companies Security groups Users Apply Security (Allocation) Actions Containers Data Data Ranges Fields Login Companies Menu Items Menu Structures Use Enquiry to determine security allocation combinations If necessary use Security processing to convert User and Profile Users to Groups Implement security model

  30. Actions – Order\Lines

  31. Containers - oeOrderFoldWin RNewman

  32. Data – 2 Fun to ABC Sports

  33. Fields– ARMCU • Jr Salesrep • Balance • Hidden • Credit Limit • Read-only • Discount • Read-only

  34. No Security Allocations • Data Ranges • Access is all or nothing • Login Companies • Only one company in original model

  35. Groups – Name field contains Group • Model based • Revoke • Grant No Overrides

  36. UI Users – Name Field contains user • Regardless of Model • Revoke Access • Not Secured Overrides

  37. Converting Users to a Group • Converting a user • All security allocations against the user being converted from is transferred to the new security group. • User is linked to the newly created security group, he becomes the first “member”. • Converting a profile user • Only security allocations common to the profile user being converted, • All users linked to the profile user will be transferred to the newly created group. • Any “non common” security allocations are not moved, and stay assigned directly to the applicable user.

  38. Demonstration • Maintenance • Allocations • Enquiry • Processing

  39. Questions and Answers • Cheryl LaBarge clabarge@progress.com • Documentation • Progress Dynamics Developer’s Guide Chapter 13 • Progress Dynamics Administration Guide Chapter 3 • Specifications • Ntdata\apps\specs\ Dynamics\2.1a\specs\group_based_security_spec.doc • IssueZilla • Search dynamics Security

More Related