Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Documentum Content Management Foundations: EMC Proven Professional Certification Exam E20-120 Study Guide

You're reading from  Documentum Content Management Foundations: EMC Proven Professional Certification Exam E20-120 Study Guide

Product type Book
Published in Jun 2007
Publisher Packt
ISBN-13 9781847192400
Pages 284 pages
Edition 1st Edition
Languages
Author (1):
Pawan Kumar Pawan Kumar
Profile icon Pawan Kumar

Table of Contents (23) Chapters

Documentum Content Management Foundations
Credits
About the Author
Acknowledgement
About the Reviewers
Preface
1. ECM Basics 2. Working with Content 3. Objects and Types 4. Architecture 5. Users and Privileges 6. Groups and Roles 7. Object Security 8. Searching 9. Custom Types 10. DocApps 11. Workflows 12. Lifecycles 13. Aliases 14. Virtual Documents Practice Test 1 Practice Test 2 Answers

Chapter 5. Users and Privileges

In this chapter, we will explore the following concepts:

  • A high-level view of Documentum security

  • Users and authentication

  • User authorization including privileges and client capabilities

  • User management

Documentum Security

At a high level, the security model in Documentum is similar to that used in contemporary enterprise applications. There are resources (information, objects) that need to be secured, there are operations that can be performed on the resources, and there are users who wish to perform these operations. The security configuration defines what is allowed for various combinations of users, operations, and resources. At run time, a user attempts to perform an operation and the components of the Documentum architecture resolve rules for the specific user, operation, and resource combination to allow or disallow the attempted operation.

At a detailed level, security implementation is very specific to the Documentum architecture. This is the first chapter...

Documentum Security


At a high level, the security model in Documentum is similar to that used in contemporary enterprise applications. There are resources (information, objects) that need to be secured, there are operations that can be performed on the resources, and there are users who wish to perform these operations. The security configuration defines what is allowed for various combinations of users, operations, and resources. At run time, a user attempts to perform an operation and the components of the Documentum architecture resolve rules for the specific user, operation, and resource combination to allow or disallow the attempted operation.

At a detailed level, security implementation is very specific to the Documentum architecture. This is the first chapter on Documentum security and introduces the concept of users and security aspects that are tied to users.

Security, in general, involves — two parts authentication and authorization. While authorization deals with what a user...

Users


The term user is typically used in one of two ways — a human interacting with a system or the representation of identity within the system. The representation of identity within the system may or may not correspond to a real human user. Such accounts are typically referred to as generic, system, or application accounts. A user is represented as an object of type dm_user within the repository.

Authentication

Typically, a user logs into an application to authenticate the claimed identity. For example, WDK applications such as Webtop and Web Publisher challenge a user with a login screen for authentication. The user selects the repository to be accessed and presents an identity as a login/password combination. The information identifying a user for the purpose of authentication is called credentials.

Once the credentials are submitted, the Content Server verifies these credentials using one or more of the following ways:

  1. 1. OS (Operating System) account: This is the default authentication...

Authorization


Recall that authorization pertains to controlling access to functionality. User-specific authorization can be enforced by the client applications as well as the Content Server. Client applications utilize a user's client capability to enforce access control for functionality within the client application. They can also utilize roles to manage access to functionality within the applications. Roles are discussed in Groups and Roles (Chapter 6).

On the other hand, Content Server utilizes basic and extended privileges to enforce access control. As we will see in later chapters, Content Server also enforces object security in addition to these privileges.

Client Capability

The client_capability property of dm_user stores the client capability level. This information is available for all users, but it is up to the client applications to utilize this information for enforcing additional access control.

Documentum's client applications such as Webtop and Desktop assign specific meanings...

User Management


As mentioned earlier, a user is stored in the repository as an object of type dm_user. No user can be authenticated against a repository without the presence of the corresponding dm_user object. Some important properties of dm_user are described below:

Help—Some DQL Queries


Here are some helpful queries related to users. These queries are based on the information presented in this chapter.

The following query retrieves some basic information about a user with login name jdoe:

SELECT user_name, user_login_name, user_address, description,
home_docbase, user_state
FROM dm_user
WHERE user_login_name = 'jdoe'

The following queries set up a new user named Jane Doe. The first query creates the user object. The second query creates a folder in the repository and the third one sets this new folder as the home folder for the new user.

CREATE dm_user OBJECT
SET user_name = 'Jane Doe',
SET user_login_name = 'jdoe',
SET user_address = 'jdoe@doquent.com',
SET user_group_name = 'docu',
SET user_source = 'inline password',
SET user_privileges = 2,
SET client_capability = 4
CREATE dm_folder OBJECT
SET object_name = 'jdoe',
SET owner_name = 'Jane Doe'
LINK '/Home'
usersDQL queriesUPDATE dm_user OBJECT
SET default_folder = '/Home/jdoe'
WHERE user_login_name...

Documentum Product Notes


User administration is typically done through Documentum Administrator. Repetitive or batch user administration activities can be scripted using DQL or API.

Checkpoint


At this point you should be able to answer the following key questions:

  1. 1. What is user authentication? What are the different ways in which Documentum supports authentication?

  2. 2. What is authorization? What are the different ways in which Documentum supports authorization specifically for a user?

  3. 3. What is the difference between privileges and client capabilities?

  4. 4. What are the different ways for creating and managing users?

Test Your Understanding


  1. 1. Authentication and authorization are one and the same (True/False).

  2. 2. For every user with OS as user source, dm_check_password is used for authentication (True/False).

  3. 3. In the following user sources, the user account must exist in the source before the corresponding user can be created in the repository:

    a. Windows OS

    b. UNIX OS

    c. LDAP

    d. None of the above

  4. 4. The database owner for the repository database is called the installation owner (True/False).

  5. 5. The client capabilities are always enforced by client applications (True/False).

  6. 6. One of the basic privileges allows document creation (True/False).

  7. 7. Create Cabinet implies Create Type privilege (True/False).

  8. 8. Superuser implies Sysadmin privilege (True/False).

  9. 9. A user cannot create another user unless the logged-in user has system administrator client capability (True/False).

  10. 10. In order to prevent a user from authenticating against the repository, the user can be deactivated (True/False).

lock icon The rest of the chapter is locked
You have been reading a chapter from
Documentum Content Management Foundations: EMC Proven Professional Certification Exam E20-120 Study Guide
Published in: Jun 2007 Publisher: Packt ISBN-13: 9781847192400
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}

Property

Label

Description

user_state

State

Active or Inactive; only active users can connect to the Content Server.

0 means that the user can log in.

1 means that the user cannot log in.

2 means that the user is locked.

3 means that the user is locked and inactive.

user_name

Name

Display name.

user_login_name

User Login Name

Login ID or user account. This is the name used for authenticating the user.

user_login_domain

User Login Domain

Windows domain or LDAP config name.

user_source

User Source

As described earlier.

description

Description

Any free-form information about the user.

user_address

E-mail Address

User's email address.

user_os_name

User OS Name

User's OS name...