Security.md
... ...
@@ -4,15 +4,15 @@ Izenda Reports fully integrates with the security of existing ASP.NET applicatio
4 4
5 5
Type of security|Example|Implementation Details
6 6
----------------|-------|----------------------
7
-[[Login]] |Users must login before gaining access to reports.|[[RequireLogin]] [[CurrentUserName]] [[CurrentUserIsAdmin]] [[Your Login Page Integration]]
8
-[[Data Sources]]|A specific user can only see certain data sources.|[[RequireLogin]] [[Basic Report Sharing]] [[VisibleDataSource]] [[Database Security]]
9
-[[User Driven Report Sharing]]|A user can save a report and decide if they want other users to see this report. They can also mark a report read-only meaning it can be viewed but not saved over.|[[Basic Report Sharing]] [[CurrentUserIsAdmin]] [[ReportsPath]] [[Read-Only & Shared Checkboxes]]
10
-[[Custom Report Control]]|Different departments can see different base reports.|[[VisibleDataSources hides reports for non-accessible datasources]] [[ReportsList may be overridden]] [[Storing Reports]] [[ReportsPath]]
11
-[[Overwriting and Deleting Reports]]|Users can load shared or base reports, but should not be able to delete them or overwrite them.|[[AllowOverwritingReports]] [[AllowDeletingReports]] [[CurrentUserIsAdmin]]
7
+[Login](#Login) |Users must login before gaining access to reports.|[[RequireLogin]] [[CurrentUserName]] [[CurrentUserIsAdmin]] [[Your Login Page Integration]]
8
+[Data Sources](#DataSources)|A specific user can only see certain data sources.|[[RequireLogin]] [[Basic Report Sharing]] [[VisibleDataSource]] [[Database Security]]
9
+[User Driven Report Sharing](#ReportSharing)|A user can save a report and decide if they want other users to see this report. They can also mark a report read-only meaning it can be viewed but not saved over.|[[Basic Report Sharing]] [[CurrentUserIsAdmin]] [[ReportsPath]] [[Read-Only & Shared Checkboxes]]
10
+[Custom Report Control](#ReportControl)|Different departments can see different base reports.|[[VisibleDataSources hides reports for non-accessible datasources]] [[ReportsList may be overridden]] [[Storing Reports]] [[ReportsPath]]
11
+[Overwriting and Deleting Reports](#DeletingReports)|Users can load shared or base reports, but should not be able to delete them or overwrite them.|[[AllowOverwritingReports]] [[AllowDeletingReports]] [[CurrentUserIsAdmin]]
12 12
[[Altering Capabilities by Role]]|Only power users should see the modify report button on the report viewer. Others will only access the report viewer.|[[ShowDesignLinks]] [[ShowModifyButton]] [[AllowOverwritingReports]] [[ShowAdminButton]]
13 13
[[Field/Record or Tenant Level Security]]|Salespeople look at the same report but see different data based on their territory and credentials. In a multi-tenant environment, reports and data for each customer, group, or tenant should be isolated.|PreExecuteReportSet - [[Hidden Filters]] [[ProcessEqualsSelectList]] [[Field & Record Level Security]]
14 14
15
-###Login Security
15
+###<a name="Login">Login Security</a>
16 16
17 17
To enable basic login security, add the following code to the PostLogin() method of your CustomAdHocConfig class. This is normally found in Global.asax file. The code should look up user credentials from your application, database or windows authentication and provide it to the Izenda Reports API. Furthermore, specifying your login page will ensure that users do not see reports without being logged in.
18 18
... ...
@@ -32,7 +32,7 @@ The method will need to be called from your login process with the following lin
32 32
Izenda.AdHoc.AdHocSettings.AdHocConfig.PostLogin()
33 33
```
34 34
35
-###Data Sources
35
+###<a href="DataSources">Data Sources</a>
36 36
37 37
The API allows control over which data sources a user sees based on their credentials. In the following example, members of the "Sales" role would see additional data sources that normal users would not. Any reports that utilize these data sources would only be visible to members of the sales role.
38 38
... ...
@@ -54,7 +54,7 @@ The method will need to be called from your login process with the following lin
54 54
Izenda.AdHoc.AdHocSettings.AdHocConfig.PostLogin()
55 55
```
56 56
57
-User Driven Report Sharing
57
+###<a href="ReportSharing">User Driven Report Sharing</a>
58 58
59 59
Once the login security is implemented, users can set the shared and read only status of a report. If a report is shared, other members of that tenant will be able to see it. If it is marked read-only, users will be able to load the report, but any modifications will need to be saved as a different report name. These limitations do not apply to users with admin rights enabled via CurrentUserIsAdmin.
60 60
... ...
@@ -67,7 +67,7 @@ public override void PostLogin()
67 67
68 68
**This is a screen shot of the Misc tab in the Report Designer showing the "Shared" & "Read Only" checkboxes that a user can select on a per report basis.**
69 69
70
-###**Custom Report Control**
70
+###<a href="ReportControl">Custom Report Control</a>
71 71
72 72
To apply additional constraints to which users see what reports, it is necessary to override the ListReports method. See Report Management for additional details.
73 73
... ...
@@ -76,7 +76,7 @@ public override Izenda.AdHoc.ReportInfo[] ListReports()
76 76
{ Return filtered list}
77 77
```
78 78
79
-###Overwriting and Deleting Reports
79
+###<a href="DeletingReports">Overwriting and Deleting Reports</a>
80 80
81 81
The API allows control of deleting or modifying reports. Reports can be accessed as Read-Only and can not be modified or deleted.
82 82