b6771bbf673131900173108ba6a4f8fec1b14010
Integration/SecurityDesignGuide.md
| ... | ... | @@ -0,0 +1,36 @@ |
| 1 | +#Security Design Guide - Under Construction |
|
| 2 | + |
|
| 3 | +[[_TOC_]] |
|
| 4 | + |
|
| 5 | +##Preface |
|
| 6 | + |
|
| 7 | +Izenda's .NET API has a number of features with associated functions and variables to plug into your application's security methodology. |
|
| 8 | + |
|
| 9 | +Izenda's security allows you to quickly and simply use case statements and your log-in credentials to implement user types and hide information per user role, group or tenant. |
|
| 10 | + |
|
| 11 | +With Izenda, you can: |
|
| 12 | + |
|
| 13 | +* Use your own authentication for Izenda |
|
| 14 | +* Separate users by name, role and/or tenant. |
|
| 15 | +* Create different user types giving access to different features |
|
| 16 | +* Filter data based on credentials automatically per user, group and/or tenant |
|
| 17 | +* Dictate which tables, views or stored procedures the user can pull data from |
|
| 18 | +* Hide reports or entire categories programatically |
|
| 19 | + |
|
| 20 | +This guide will explain the different variables and methods to implement security and explain common scenarios using working code samples. |
|
| 21 | + |
|
| 22 | +##Section 1 - Commonly Used Variables |
|
| 23 | + |
|
| 24 | +A collection of commonly used variables with short descriptions and use cases. |
|
| 25 | + |
|
| 26 | +##Section 2 - Log-in Credentials |
|
| 27 | + |
|
| 28 | +A best practice document with an example using the a sample Log in page. |
|
| 29 | + |
|
| 30 | +##Section 3 - Getting started |
|
| 31 | + |
|
| 32 | +A basic security foundation with example code |
|
| 33 | + |
|
| 34 | +##Section 4 - User Types |
|
| 35 | + |
|
| 36 | +An intermediate code sample showing a case statement based on user role |
|
| ... | ... | \ No newline at end of file |