(file) Return to User_Credential.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIMPrelim29

File: [Pegasus] / pegasus / Schemas / CIMPrelim29 / Attic / User_Credential.mof (download)
Revision: 1.2, Thu Feb 24 20:47:33 2005 UTC (19 years, 3 months ago) by a.dunfey
Branch: MAIN
CVS Tags: TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP348_SCMO-merged_out_from_trunk, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, TASK-PEP311_WSMan-root, TASK-PEP311_WSMan-branch, RELEASE_2_5_0-RC1, HPUX_TEST, HEAD
Changes since 1.1: +4 -4 lines
FILE REMOVED
PEP#: 215
TITLE: Remove old schemas

DESCRIPTION:

Removing old, unneeded schema files from the repository:

CIM 2.7
CIM 2.7.1 Preliminary
CIM 2.8 Preliminary
CIM 2.9 Preliminary

// ===================================================================
// Title:         User-Security General Credentials
// $State: dead $
// $Date: 2005/02/24 20:47:33 $
// $Source: /cvs/MSB/pegasus/Schemas/CIMPrelim29/Attic/User_Credential.mof,v $
// $Revision: 1.2 $
// ===================================================================
//#pragma inLine ("Includes/copyright.inc")
// Copyright 1998-2004 Distributed Management Task Force, Inc. (DMTF).
// All rights reserved.
// DMTF is a not-for-profit association of industry members dedicated
// to promoting enterprise and systems management and interoperability.
// DMTF specifications and documents may be reproduced for uses
// consistent with this purpose by members and non-members,
// provided that correct attribution is given.
// As DMTF specifications may be revised from time to time,
// the particular version and release date should always be noted.
// 
// Implementation of certain elements of this standard or proposed
// standard may be subject to third party patent rights, including
// provisional patent rights (herein "patent rights"). DMTF makes
// no representations to users of the standard as to the existence
// of such rights, and is not responsible to recognize, disclose, or
// identify any or all such third party patent right, owners or
// claimants, nor for any incomplete or inaccurate identification or
// disclosure of such rights, owners or claimants. DMTF shall have no
// liability to any party, in any manner or circumstance, under any
// legal theory whatsoever, for failure to recognize, disclose, or
// identify any such third party patent rights, or for such party's
// reliance on the standard or incorporation thereof in its product,
// protocols or testing procedures. DMTF shall have no liability to
// any party implementing such standard, whether such implementation
// is foreseeable or not, nor to any patent owner or claimant, and shall
// have no liability or responsibility for costs or losses incurred if
// a standard is withdrawn or modified after publication, and shall be
// indemnified and held harmless by any party implementing the
// standard from any and all claims of infringement by a patent owner
// for such implementations.
// 
// For information about patents held by third-parties which have
// notified the DMTF that, in their opinion, such patent may relate to
// or impact implementations of DMTF standards, visit
// http://www.dmtf.org/about/policies/disclosures.php.
//#pragma inLine
// ===================================================================
// Description: The User Model extends the management concepts that
//              are related to users and security.
//              This file defines the generic concepts of a
//              credential.
// 
//              The object classes below are listed in an order that
//              avoids forward references. Required objects, defined
//              by other working groups, are omitted.
// ===================================================================
// Change Log for v2.9 Preliminary
//   CR1222 - Define a CredentialContext association
// Change Log for v2.8 Final
//   CR1218 - Accepted all changes for CIM V2.8 Prelim, except removed
//           BiometricCredential from the Final release and into
//           CIM V2.9 Preliminary.
// 
// Change Log for v2.8 Preliminary
//  CR1011 - Added BiometricCredential, updated Credential.Description.
//  CR1014 - Removed Min (1) from ManagedCredential.Antecedent
// 
// Change Log for v2.7
//   CR784 - Promoted 2 properties, Issued and Expired, from
//          CIM_KerberosTicket to CIM_Credential
//   CR980 - Removed Experimental qualifier from 2 properties in
//          Credential
// ===================================================================

#pragma Locale ("en_US")


// ==================================================================
// Credential
// ==================================================================
   [Abstract, Version ( "2.8.0" ), Description (
       "Subclasses of CIM_Credential define materials, information or "
       "other data which are used to establish identity. Generally, "
       "there may be some shared information, or credential material "
       "which is used to identify and authenticate an entity in the "
       "process of gaining access to, or permission to use, resources. "
       "Such credential material may be used to authenticate an "
       "entity's identity initially, as done by a "
       "CIM_AuthenticationService, and additionally on an ongoing "
       "basis (for example, during the course of a connection or other "
       "security association), as proof that each received message or "
       "communication came from a valid 'user' of that credential "
       "material.")]
class CIM_Credential : CIM_ManagedElement {

      [Description (
          "The date and time when the credential was issued. Use a "
          "value of all 0s if this information is not applicable.")]
   datetime Issued;

      [Description (
          "The date and time when the credential expires (and is not "
          "appropriate for use for authentication/ authorization). Use "
          "a value of all 9s if this information is not applicable. "
          "Note that this property does not define how the expiration "
          "is set - but that there IS an expiration. The property may "
          "be set to either a specific date/time or an interval "
          "(calculated from the Issued datetime). For example, for "
          "Certificate Authority-signed public key, the expiration is "
          "determined by the CA. Another example is a voice mail "
          "password that expires 60 days after it is set/issued.")]
   datetime Expires;
};


// ===================================================================
// ManagedCredential
// ===================================================================
   [Association, Version ( "2.8.0" ), Description (
       "This relationship associates a CredentialManagementService "
       "with the Credential it manages.")]
class CIM_ManagedCredential : CIM_Dependency {

      [Override ( "Antecedent" ), Max ( 1 ), Description (
          "The credential management service.")]
   CIM_CredentialManagementService REF Antecedent;

      [Override ( "Dependent" ), Description (
          "The managed credential.")]
   CIM_Credential REF Dependent;
};

// ==================================================================
// CredentialContext
// ==================================================================
   [Association, Experimental, Version ( "2.8.1000" ), Description (
       "This relationship defines the context (for example, a System "
       "Service) of a Credential. Without it, only the "
       "ManagedCredential association exists to establish the "
       "'context' of a Credential. ManagedCredential is an association "
       "from a Credential to a CredentialManagementService. However, "
       "it is not necessarily true that a CredentialManagementService "
       "provides unique context for the credential. It may "
       "authenticate credentials for multiple contexts (for example, "
       "multiple systems or services), or a credential may be "
       "authenticated by multiple services. It is necessary to "
       "separately define the 'context' of the Credential, via this "
       "association.")]
class CIM_CredentialContext {

      [Key, Description (
          "A Credential whose context is defined.")]
   CIM_Credential REF ElementInContext;

      [Key, Description (
          "The ManagedElement that provides context or scope for the "
          "Credential.")]
   CIM_ManagedElement REF ElementProvidingContext;
};

// ===================================================================
// end of file
// ===================================================================

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2