[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: ftcstr attribute replacement ?
On 06/30/2013 06:22 PM, Emmanuel LÃcharny wrote:
Le 7/1/13 1:12 AM, Shawn McKinney a Ãcrit :
Can these attrs be multi-occurring and still attached to same node?
User may have many roles assigned, each can be constrained differently.
The ftCStr is declared as a SINGLE VALUE attribute.
In fortress there are 3 temporal constraints that hang off user node:
1. user contraint: (single)
# A13: User Temporal Constraint, type STRING, SINGLE VALUE
attributetype ( 1.3.6.1.4.1.1.38088.1.13
NAME 'ftCstr'
DESC 'Fortress User Temporal Constraint'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
2. user-role constraint: (multi-occurring)
# A15: User Role Constraints, type STRING, MULTI VALUE
attributetype ( 1.3.6.1.4.1.1.38088.1.15
NAME 'ftRC'
DESC 'Fortress User Role Constraints'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
3. user-admin-role constraint: (multi-occurring)
# A21: Admin Role Constraints, type STRING, MULTI VALUE
attributetype ( 1.3.6.1.4.1.1.38088.1.21
NAME 'ftARC'
DESC 'Fortress Admin Role Constraints'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
--
shawn.mckinney@jts.us is my new email address