JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris WBEM Developer's Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information

Preface

1.  Overview of Solaris Web-Based Enterprise Management

2.  Using the CIM Object Manager

3.  Using the Sample Programs

4.  Writing a Client Program

5.  Writing WBEM Queries

6.  Writing a Provider Program

7.  Creating JavaBeans Components Using the MOF Compiler

8.  Administering Security

WBEM Security Mechanisms

Client Authentication

Role Assumption

Secure Messaging

Authorization

Auditing

Logging

Using Sun WBEM User Manager to Set Access Control

What You Can and Cannot Do With Sun WBEM User Manager

Using Sun WBEM User Manager

How to Start Sun WBEM User Manager

How to Grant Default Access Rights to a User

How to Change Access Rights for a User

How to Remove Access Rights for a User

How to Set Access Rights for a Namespace

How to Remove Access Rights for a Namespace

Using the Solaris WBEM SDK APIs to Set Access Control

Solaris_UserAcl Class

How to Set Access Control for a User

Solaris_NamespaceAcl Class

How to Set Access Control for a Namespace

Troubleshooting Problems With WBEM Security

If a Client (User) Cannot Be Authenticated by the CIMOM on the WBEM Server

If Other CIM Security Exception Errors Appear

If an Authorization Check Fails

9.  Troubleshooting

A.  Solaris Schema

Index

Using Sun WBEM User Manager to Set Access Control

Sun WBEM User Manager (wbemadmin) enables you and other privileged users to perform the following tasks:


Note - The user for whom you specify access control must have a Solaris user account.


What You Can and Cannot Do With Sun WBEM User Manager

You can set access privileges for individual namespaces or for a combination of a user and a namespace. When you add a user and select a namespace, the user is granted read access to CIM objects in the selected namespace by default.


Note - An effective way to combine user and namespace access rights is to start by restricting access to a namespace. Then grant individual users read, read and write, or write access to that namespace.


You cannot set access rights on individual managed objects. However, you can set access rights for all managed objects in a namespace as well as on a per-user basis.

If you log in as root, you can set the following types of access to CIM objects: