HP Visualize J210 HP-UX DMI 2.0 Developer's Guide: HP-UX/HP 9000 Computers, H - Page 31
Security Token Handling
View all HP Visualize J210 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 31 highlights
Modified Definition (tabular) Component Interface Concepts Group-Level Security Start Group Name = "System Memory Group" Class = "HP|System Memory Group|001" ID = 2 Key = 2 Start Attribute Name = "Total Physical Memory" ID = 1 Storage = Specific Access = Read-Write Type = int64 Value = 0 End Attribute Start Attribute Name = "Security Token" ID = 2 Type = "OctetString" Access = Read-Only Value = "" End Attribute End Group Securing an existing tabular group is much like securing a scalar group. First, add a new Security Token attribute to the group definition. Next, augment the existing keylist definition to include this new attribute. The Security Token then becomes one of the attributes comprising a unique row. This means that it is required for any get or set command on the table. Additionally, DmiAddRow() and DmiDeleteRow() calls require a valid keylist. Thus, they also require the Security Token. Security Token Handling Alternatively, HP provides a library with a security token-generating procedure and a security token validation procedure. Management applications can use these procedures to secure access to protected attribute values. Additionally, HP provides a library to management application writers that wish to retrieve protected attributes from HP's implementation of the Unix Standards Group Definition (Unix MIF). This library contains the security token-generating procedure. These two procedures are: • GenerateToken() • ValidateToken() For detailed information, see the generateToken(3X) and validateToken(3X) manpages. Chapter 3 31