(file) Return to CIM_Credential.mof CVS log (file) (dir) Up to [Pegasus] / pegasus / Schemas / CIM231 / DMTF / User

File: [Pegasus] / pegasus / Schemas / CIM231 / DMTF / User / CIM_Credential.mof (download)
Revision: 1.1, Tue Jan 24 13:50:36 2012 UTC (12 years, 5 months ago) by marek
Branch: MAIN
CVS Tags: preBug9676, postBug9676, TASK-TASK_PEP362_RestfulService_branch-root, TASK-TASK_PEP362_RestfulService_branch-merged_out_from_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_to_trunk, TASK-TASK_PEP362_RestfulService_branch-merged_in_from_branch, TASK-TASK_PEP362_RestfulService_branch-branch, TASK-PEP362_RestfulService-root, TASK-PEP362_RestfulService-merged_out_to_branch, TASK-PEP362_RestfulService-merged_out_from_trunk, TASK-PEP362_RestfulService-merged_in_to_trunk, TASK-PEP362_RestfulService-merged_in_from_branch, TASK-PEP362_RestfulService-branch, TASK-PEP317_pullop-merged_out_from_trunk, TASK-PEP317_pullop-merged_in_to_trunk, RELEASE_2_14_1, RELEASE_2_14_0-RC2, RELEASE_2_14_0-RC1, RELEASE_2_14_0, RELEASE_2_14-root, RELEASE_2_14-branch, RELEASE_2_13_0-RC2, RELEASE_2_13_0-RC1, RELEASE_2_13_0-FC, RELEASE_2_13_0, RELEASE_2_13-root, RELEASE_2_13-branch, RELEASE_2_12_1-RC1, RELEASE_2_12_1, RELEASE_2_12_0-RC1, RELEASE_2_12_0-FC, RELEASE_2_12_0, RELEASE_2_12-root, RELEASE_2_12-branch, HEAD, CIMRS_WORK_20130824
Branch point for: TASK-PEP317_pullop-branch
BUG#:9155
TITLE: Upgrade Pegasus to Include the CIM 2.31 Schema in CVS

DESCRIPTION:

// Copyright (c) 2005 DMTF.  All rights reserved.
// <change cr="DMTFCR01514" type = "change"> Fix description of
// timestamp in Credential </change>
// <change cr="ArchCR00066.004" type="add">Add UmlPackagePath
// qualifier values to CIM Schema.</change>
// ==================================================================
//  CIM_Credential
// ==================================================================
   [Abstract, Version ( "2.8.0" ), 
    UMLPackagePath ( "CIM::User::Credential" ), 
    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 \'00000101000000.000000+000\', (midnight, "
          "January 1, 1 BCE at coordinated universal time +0 "
          "minutes), if this information is not applicable. On "
          "CreateInstance, if this property is unspecified, or set "
          "to NULL, then current time is assumed." )]
   datetime Issued;

      [Description ( 
          "The date and time when the credential expires (and is "
          "not appropriate for use for authentication/ "
          "authorization). If this information is not applicable, "
          "Use a value of \'99991231235959.999999+999\', (1 "
          "microsecond before midnight, December 31, 9999 CE, at "
          "coordinated universal time + 999 minutes). \n"
          "On CreateInstance, if this property is unspecified, or "
          "set to NULL, then a value of \'99991231235959.999999+999\' "
          "is assumed. 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;


};

No CVS admin address has been configured
Powered by
ViewCVS 0.9.2