You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,15 +41,16 @@ The new RBAC allows more granular permissions, improved flexibility and greater
41
41
42
42
The system-defined roles shipped with NetBackup also changed from 8.1.2 to the 8.3 release. In 8.1.2, there were three system-defined roles available for RBAC configuration. In the 8.3 release, this was simplified to offer a single “Administrator” role which has all privileges for RBAC.
43
43
44
-
Due to the significant design shift, automatic upgrade conversion of 8.1.2 RBAC roles to the new 8.3 roles is not feasible. However, tools are available to migrate the Backup administrator role and create a new Security administrator role for the users that had the old RBAC Security administrator role. Other roles must be reconfigured manually.
44
+
Due to the significant design shift, automatic upgrade conversion of 8.1.2 RBAC roles to the new 8.3 roles is not feasible. However, tools are available to migrate the Backup administrator role and create a new Security administrator role for the users that had the old RBAC Security administrator role.
45
+
Other roles must be reconfigured manually.
45
46
There is also a script in this repository available to generate templated NetBackup roles.
46
-
See **/recipes/perl/rbac-roles/rbac_role_templates.pl**
47
+
See **/recipes/perl/access-control/rbac_role_templates.pl**
47
48
48
49
49
50
Any API keys in use prior to upgrade will still be valid, however, the underlying access granted those API keys must
50
51
be reconfigured using the new RBAC configuration, after which any active user sessions must be removed.
51
52
A utility script exists in this repository to help convert active API keys after upgrade to NetBackup 8.3.
52
53
See **/recipes/perl/access-control/access_control_api_requests.pl**
53
54
54
-
Most of the API examples in this repository assume a valid JWT (Json Web Token) or API Key issued by NetBackup and do not incorporate role configuration as part of the script.
55
-
However, there may be some examples which do configure RBAC as part of the script and have not yet been updated to use the RBAC design.
55
+
Most of the API examples in this repository assume a valid JWT (Json Web Token) or API Key issued by NetBackup and do
56
+
not incorporate role configuration as part of the script. However, there may be some examples which do configure RBAC as part of the script and have not yet been updated to use the RBAC design.
This directory contains code samples for converting RBAC principals behind registered API keys.
4
-
3
+
This directory contains scripts and code samples to aid in the migration of NetBackup 8.1.2
4
+
roles to the new 8.3 design as well as scripts that can be used to generate typical roles using the new RBAC design.
5
+
5
6
## Disclaimer
6
7
7
8
These scripts are only meant to be used as reference. They are not intended to be used in production environment.
@@ -13,10 +14,26 @@ These scripts are only meant to be used as reference. They are not intended to b
13
14
14
15
## Executing the recipes in Perl
15
16
16
-
Use the following command to get RBAC principals behind registered API keys, get existing roles for RBAC gen1 roles, and create new access control roles accordingly.
17
+
**Examples of updating access control roles used by API Keys.**
18
+
Use the following commands to get RBAC principals behind registered API keys, get existing 0roles for RBAC gen1 roles
19
+
, and create new access control roles accordingly.
0 commit comments