Table of Contents

1. Introduction to DCE Application Programming

• 1.1. Development Overview
• 1.2. Overview of DCE Application Development Steps
• 1.3. Application Development Tools
• 1.3.1. DCE UUID Generator
• 1.3.2. DCE Interface Definition Language
• 1.3.3. DCE IDL Compiler
• 1.3.4. Attribute Configuration File
• 1.3.5. DCE Host Daemon
• 1.3.6. DCE API
• 1.3.7. DCE Control Program
• 1.4. The Interface Definition
• 1.4.1. Generate the Interface UUID
• 1.4.2. Write the Interface Definition File
• 1.4.3. Write the Attribute Configuration File (ACF)
• 1.4.4. Process the Files with the IDL Compiler
• 1.5. The Server Initialization
• 1.5.1. Setup for Serviceability
• 1.5.2. Setup the Server's Objects
• 1.5.2.1. Object UUIDs in Bindings
• 1.5.2.2. Make Object-UUID/Type-UUID Associations
• 1.5.2.3. Summary of the Mechanisms that Rely on Object UUIDs
• 1.5.3. Setup Security
• 1.5.4. Define the Manager Entry Point Vectors for Each Set of Operations
• 1.5.5. Register the Server
• 1.5.5.1. Register the Interface, Type UUID, and EPV with RPC Runtime
• 1.5.5.2. Tell RPC Runtime What Protocol Sequences to Use
• 1.5.5.3. Register the Binding Information with the Endpoint Mapper Service
• 1.5.5.4. Export the Binding Information to the Namespace (CDS)
• 1.5.6. Specify Multithreadedness
• 1.5.7. Listen for Incoming Service Requests
• 1.5.8. Cleanup Code When the Server Terminates
• 1.5.8.1. Unregister The Server
• 1.5.8.2. Unexport From the Namespace
• 1.5.8.3. Cleanup Security Information
• 1.6. The Client Binding and RPC Invocation
• 1.6.1. Import the Binding Information from the Namespace
• 1.6.1.1. Getting a Handle
• 1.6.1.2. Entry Name
• 1.6.1.3. Binding Compatibility
• 1.6.2. Annotate the Binding Handle for Security
• 1.6.2.1. Preparation
• 1.6.2.2. Setting Up for Authenticated RPC
• 1.6.3. Invoke Remote Procedure Calls
• 1.6.3.1. The Possibility of Binding Failure
• 1.6.3.2. The Result of Successful Binding
• 1.7. The Server's Manager of RPC Requests
• 1.7.1. Get the Client's Credentials
• 1.7.2. Get the Object's Access Control List (ACL)
• 1.7.3. Make the Authorization Decision
• 1.7.4. Service the RPC Request
• 1.7.5. Return the Results and Resume Listening
• 1.7.5.1. Continue
• 1.8. About DCE Programming Style
• 1.8.1. Mechanism, Policy, and Style
• 1.8.2. Policy and Style Issues
• 1.8.3. General Policies

2. Threads

• 2.1. Thread Use Policy
• 2.1.1. To Thread or Not to Thread
• 2.1.2. How Many Threads?
• 2.1.3. Scheduling Policies
• 2.2. Thread Safety
• 2.2.1. Thread Rules
• 2.3. Threads Programming Topics
• 2.3.1. Thread Handles
• 2.3.2. Storage for Thread Specific Data
• 2.3.3. Cancelling Threads
• 2.3.3.1. Cancellability State
• 2.3.3.2. Cancellation Points
• 2.3.3.3. Cancellation Side Effects
• 2.3.3.4. Thread Cleanup
• 2.3.3.5. Asynchronous Cancel Safety
• 2.3.3.6. Cancel Rules Summary
• 2.3.4. Signals
• 2.3.4.1. Signal Masking
• 2.3.4.2. Synchronous Signal Handling
• 2.3.4.3. Asynchronous Signal Handling
• 2.3.4.4. Signal Rules
• 2.3.5. Forking in a Threaded Application
• 2.4. RPC Threads
• 2.4.1. RPC Cancel Semantics

3. Security

• 3.1 The Basic Security Model
• 3.2 Application Roles
• 3.3. Authentication Model
• 3.3.1. The DCE Authentication Model
• 3.3.2. Application-Level Authentication
• 3.3.3. Obtaining an Authentication Identity
• 3.3.4. The Authenticated RPC Call
• 3.3.5. Managing Keys
• 3.3.6. Default Server Authentication Steps
• 3.3.6.1. managekey
• 3.3.6.2. server_get_identity
• 3.3.6.3. server_renew_identity
• 3.3.6.4. is_valid_principal
• 3.4. Authorization
• 3.4.1. Client Credentials
• 3.4.2. Access Control Lists
• 3.4.2.1. Permissions Semantics Reccomendations
• 3.4.3. ACL Managers
• 3.4.3.1. Who Does What?
• 3.4.3.2. The Requirements
• 3.4.3.3. What is an Object?
• 3.4.3.4. Why Three Databases?
• 3.4.3.5. Object Name Resolution Routine
• 3.4.3.6. What is an ACL Manager?
• 3.4.3.7. Why Two ACL Managers?
• 3.4.3.8. How the ACL Library Routines Extract and Evaluate ACLs
• 3.4.3.9. Backing Store Database Items and Headers
• 3.4.3.10. Object-Indexed Store
• 3.4.3.11. Name-Indexed Store
• 3.4.3.12. ACL UUID-Indexed Store
• 3.4.3.13. ACL Manager Coding Example
• 3.4.3.14. Data Definitions
• 3.4.3.15. server_get_local_principal_id
• 3.4.3.16. server_create_acl
• 3.4.3.17. server_store_acl
• 3.4.3.18. server_acl_mgr_setup
• 3.4.3.19. server_acl_mgr_close
• 3.4.3.20. server_rdacl_export
• 3.4.3.21. server_rdacl_cleanup
• 3.4.3.22. sample_mgmt_auth
• 3.4.3.23. sample_resolve_by_name

4. Binding

• 4.1. The Binding Model
• 4.1.1. Server Binding Model
• 4.1.2. Client Binding Model
• 4.1.3. Call Routing
• 4.1.4. Routing Policy
• 4.1.4.1. Object UUIDs as Endpoint Identifiers
• 4.2. Binding Handles
• 4.3. Binding Methods
• 4.3.1. Authentication and Binding Methods

5. Using the DCE Name Service

• 5.1. Introduction to Using NSI
• 5.1.1. The UUID
• 5.1.2. Object UUIDs
• 5.1.3. Interface UUIDs
• 5.1.4. Summary: Names and UUIDs
• 5.2. Binding to an Object
• 5.3. Junctions
• 5.3.1. A Junction Example
• 5.3.2. Junctions and the ACL Editor
• 5.4. Name Service Terminology
• 5.4.1. CDS Entries
• 5.4.2. CDS Entry Attributes
• 5.5. Binding
• 5.5.1. Importing and Exporting Bindings
• 5.5.2. Summary
• 5.6. Partial Binding and the Endpoint Mapper
• 5.7. Interface Ambiguity and Partial Bindings
• 5.8. Using Object UUIDs to Avoid Binding Ambiguity
• 5.9. An Object-Oriented Namespace
• 5.10. Setting Up an Object-Oriented Namespace
• 5.11. Groups and Profiles
• 5.11.1. Group Entries
• 5.11.2. Profiles
• 5.11.3. Summary of Namespace Entry Types
• 5.12. Three Models for Accessing Binding Information
• 5.12.1. Access By Services
• 5.12.2. Access By Servers
• 5.12.3. Access By Objects
• 5.12.4. Summary of Binding Models
• 5.13. Models Based on Non-CDS Databases
• 5.13.1. Example of a Privately Managed Database
• 5.13.2. Combining Models
• 5.14. An Object-Oriented Model with Grouped Binding Information
• 5.15. Server and Client Steps
• 5.15.1. Server Export
• 5.15.2. Client Import
• 5.16. Global Organization of the Namespace

6. RPC Parameters

• 6.1. Execution Semantics
• 6.2. Parameter Semantics
• 6.2.1. Parameter Memory Management
• 6.2.1.1. Client Side Allocation
• 6.2.1.2. Server Side Allocation
• 6.3. RPC Data Types
• 6.3.1. IDL to C Type Mappings
• 6.3.2. Character Handling
• 6.3.3. Pointers
• 6.3.3.1. Memory Allocation Routines
• 6.3.3.2. Pointer Types
• 6.3.3.3. Pointer Examples
• 6.3.4. Context Handles
• 6.3.5. Arrays
• 6.3.6. Structures and Unions
• 6.3.7. Pipes
• 6.3.8. The transmit_as Attribute

7. Errors and Messaging

• 7.1. Error Handling
• 7.2. Messaging Facilities
• 7.2.1. DCE Errors and DCE Messages
• 7.2.2. DCE Application Message APIs
• 7.3. Serviceability and Logging
• 7.4. Sample Code

8. Server Management

• 8.1. Application Support for Server Management
• 8.2. Manager Initialization

A. A Sample Application

• A.1. The Generic Server
• A.2. Object Bind Interface
• A.3. Manager and Client Illustrations
• A.4. Message (sams) File
• A.5. Makefile