Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sramInactiveDays not treated as real attributes #132

Closed
baszoetekouw opened this issue Jun 12, 2024 · 2 comments
Closed

sramInactiveDays not treated as real attributes #132

baszoetekouw opened this issue Jun 12, 2024 · 2 comments
Milestone

Comments

@baszoetekouw
Copy link
Member

sramInactiveDays seems te be treated as an operational attribute

@mrvanes
Copy link
Contributor

mrvanes commented Jun 20, 2024

Ik heb werkelijk geen idee waarom deze ldif een operational attribute op zou leveren?

dn: cn=sramPerson,cn=schema,cn=config
objectClass: olcSchemaConfig
cn: sramPerson
olcAttributeTypes: ( 1.3.6.1.4.1.1076.20.100.20.2.1 NAME 'sramInactiveDays'
  DESC 'Number of days this entity was inactive'
  EQUALITY IntegerMatch
  ORDERING IntegerOrderingMatch
  SYNTAX 1.3.6.1.4.1.1466.115.121.1.27
  )
olcObjectClasses: ( 1.3.6.1.4.1.1076.20.100.20.1.1 NAME 'sramPerson'
  AUXILIARY
  MAY (
    sramInactiveDays
    )
  )

En met een verse LDAP database kan ik het ook niet meer reproduceren. Het sramPerson object is aangepast (voorheen had het twee extra MAY attributen) en heeft nu alleen nog sramInactiveDays, dat gooit blijkbaar roet in het eten?

Image

@mrvanes mrvanes closed this as completed Jun 20, 2024
@mrvanes mrvanes moved this from Todo to To be tested in SRAM development Jun 20, 2024
@baszoetekouw
Copy link
Member Author

Ok, dan zou dit automaytisch moeten worden gefixed als we de ldap straks overzetten naar de SC infra.

@baszoetekouw baszoetekouw moved this from To be tested to Done in SRAM development Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants