Skip to content

Latest commit

 

History

History
361 lines (291 loc) · 8.73 KB

File metadata and controls

361 lines (291 loc) · 8.73 KB

voPosixAccount v2.0.0


Creative Commons License

This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.

Copyright © 2022 by the respective authors.


Introduction

In many virtual organizations, it is desirable to reflect cluster information on the person's LDAP record (as opposed to in a standalone LDAP entry), and it may be necessary to reflect multiple accounts on different clusters. This is not possible with the posixAccount schema, which dates from 1998, as almost all attributes are defined as SINGLE-VALUE.

voPosixAccount is basically an update to the posixAccount, with the core attributes in support of this use case redefined without the SINGLE-VALUE limitation. The voPosixAccount and voPosixGroup object classes replace the legacy definitions with definitions permitting multiple values.

voPosixAccount Attribute Options

In order to support multiple values in the same object, it must be possible to identify which attributes are associated with which accounts. voPosixAccount uses attribute options. For more information on attribute options, see the main voPerson document.

scope-* Attribute Description Option

All voPosixAccount attributes are expected to use a scoping label to denote the cluster for which that value is valid. The value of the scoping label is meaningful only in the local context, and should otherwise be treated as opaque except for comparison purposes (caseExactMatch).

voPosixAccount Object Class and Attributes

voPosixAccount Object Class Definition

( 1.3.6.1.4.1.25178.4.2
  NAME 'voPosixAccount'
  AUXILIARY
  MUST ( cn $
         uid $
         voPosixAccountUidNumber $
         voPosixAccountGidNumber $
         voPosixAccountHomeDirectory )
  MAY ( voPosixAccountLoginShell $
        voPosixAccountGecos ) 
)

voPosixAccountGecos Attribute Definition

OID 1.3.6.1.4.1.25178.4.2.1
RFC4512 Definition
( 1.3.6.1.4.1.25178.4.2.1
        NAME 'voPosixAccountGecos'
        DESC 'voPerson domain specific GECOS field'
        EQUALITY caseIgnoreMatch
        SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
Multiple Values? Yes
Attribute Options
  • scope-cluster: Denotes cluster for which this value is valid

Definition

The GECOS field for the cluster account.

Example

voPosixAccountGecos;scope-hpc: Pat X Lee
voPosixAccountGecos;scope-lab: Pat Lee,,,

voPosixAccountGidNumber Attribute Definition

OID 1.3.6.1.4.1.25178.4.2.2
RFC4512 Definition
( 1.3.6.1.4.1.25178.4.2.2
        NAME 'voPosixAccountGidNumber'
        DESC 'voPerson domain specific primary group identifier'
        EQUALITY integerMatch
        SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' )
Multiple Values? Yes
Attribute Options
  • scope-cluster: Denotes cluster for which this value is valid

Definition

The primary group identifier for the cluster account.

Example

voPosixAccountGidNumber;scope-hpc: 1008
voPosixAccountGidNumber;scope-lab: 10008

voPosixAccountHomeDirectory Attribute Definition

OID 1.3.6.1.4.1.25178.4.2.3
RFC4512 Definition
( 1.3.6.1.4.1.25178.4.2.3
        NAME 'voPosixAccountHomeDirectory'
        DESC 'voPerson domain specific absolute path to the home directory'
        EQUALITY caseExactMatch
        SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
Multiple Values? Yes
Attribute Options
  • scope-cluster: Denotes cluster for which this value is valid

Definition

The home directory for the cluster account.

Example

voPosixAccountHomeDirectory;scope-hpc: /home/plee
voPosixAccountHomeDirectory;scope-lab: /users/p/plee

voPosixAccountLoginShell Attribute Definition

OID 1.3.6.1.4.1.25178.4.2.4
RFC4512 Definition
( 1.3.6.1.4.1.25178.4.2.4
        NAME 'voPosixAccountLoginShell'
        DESC 'voPerson domain specific path to the login shell'
        EQUALITY caseExactMatch
        SYNTAX '1.3.6.1.4.1.1466.115.121.1.15' )
Multiple Values? Yes
Attribute Options
  • scope-cluster: Denotes cluster for which this value is valid

Definition

The login shell for the cluster account.

Example

voPosixAccountLoginShell;scope-hpc: /bin/bash
voPosixAccountLoginShell;scope-lab: /bin/tcsh

voPosixAccountUidNumber Attribute Definition

OID 1.3.6.1.4.1.25178.4.2.5
RFC4512 Definition
( 1.3.6.1.4.1.25178.4.2.5
        NAME 'voPosixAccountUidNumber'
        DESC 'voPerson domain specific unique user identifier'
        EQUALITY integerMatch
        SYNTAX '1.3.6.1.4.1.1466.115.121.1.27' )
Multiple Values? Yes
Attribute Options
  • scope-cluster: Denotes cluster for which this value is valid

Definition

The UID number for the cluster account.

Example

voPosixAccountUidNumber;scope-hpc: 1008
voPosixAccountUidNumber;scope-lab: 10008

voPosixGroup Object Class

voPosixGroup Object Class Definition

( 1.3.6.1.4.1.25178.4.3
  NAME 'voPosixGroup'
  AUXILIARY
  MUST ( cn $ voPosixAccountGidNumber )
  MAY ( memberUid )
)

Sample LDIF

dn: voPersonID=V097531, ou=People, dc=myvo, dc=org
objectClass: person
objectClass: organizationalPerson
objectClass: inetOrgPerson
objectClass: voPerson
objectClass: voPosixAccount
cn: Patricia Q Lee
displayName: Pat Lee
givenName: Patricia
sn: Lee
uid;scope-hpc: pxlee
uid;scope-lab: plee
voPosixAccountUidNumber;scope-hpc: 1008
voPosixAccountUidNumber;scope-lab: 10008
voPosixAccountGidNumber;scope-hpc: 1008
voPosixAccountGidNumber;scope-lab: 10008
voPosixAccountHomeDirectory;scope-hpc: /home/plee
voPosixAccountHomeDirectory;scope-lab: /users/p/plee
voPosixAccountLoginShell;scope-hpc: /bin/bash
voPosixAccountLoginShell;scope-lab: /bin/tcsh
voPosixAccountGecos;scope-hpc: Pat X Lee
voPosixAccountGecos;scope-lab: Pat Lee,,,
voPersonCertificateDN;scope-cert1: CN=Pat Lee A251,O=Example,C=US,DC=cilogon,DC=org
voPersonCertificateIssuerDN;scope-cert1: CN=CILogon Basic CA 1, O=CILogon, C=US, DC=cilogon, DC=org
voPersonID: V097531
voPersonStatus: active

References

  1. RFC 2307 posixAccount Object Class Specification

Changelog

voPersonAccount version numbers correlate to the latest voPerson version at the time of the most recent change. For example, if voPerson is at version 2.0.1 and voPosixAccount is at version 2.0.0, then there are no changes to this document since voPerson 2.0.0.

  • voPosixAccount and voPosixGroup were introduced with voPerson 2.0.0.