remove the obligation to have an gosaAccount on user entries to be displayed by FusionDirectory

hello,

to be more clear about that, the first step is to remove the obligation to have an gosaAccount to be listed by FusionDirectory

The second step will be to see how to make the attributes present in the gosaAccount be put in another classical schema or not

Cheers

(from redmine: written on 2014-11-12)

By bmortier on 2017-09-02T15:14:48 (imported from GitLab)

uid -> already in inetOrgPerson (but not required) gosaDefaultLanguage -> not used anymore. We use preferredLanguage from inetOrgPerson gosaLoginRestriction -> specific to us. What should we do? academicTitle $ personalTitle $ dateOfBirth $ gender -> there is no standard attributes for these ones. dateOfBirth seems pretty important. All this can go in an activable FD tab but this seems not ideal for users using these fields a lot.

sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $ sambaBadPasswordCount $ sambaBadPasswordTime $ -> all of these are not set anymore in 1.0.9 unless samba tab is active. This means after activating samba one need to re-set the password.

(from redmine: written on 2014-11-12)

By Côme Chilliet on 2017-09-02T15:14:49 (imported from GitLab)

Côme BERNIGAUD wrote:

uid -> already in inetOrgPerson (but not required)

ok

gosaDefaultLanguage -> not used anymore. We use preferredLanguage from inetOrgPerson

ok

gosaLoginRestriction -> specific to us. What should we do?

change to fdLoginRestriction

academicTitle $ personalTitle $ dateOfBirth $ gender -> there is no standard attributes for these ones. dateOfBirth seems pretty important. All this can go in an activable FD tab but this seems not ideal for users using these fields a lot.

not at all so this is blocking us

sambaLMPassword $ sambaNTPassword $ sambaPwdLastSet $ sambaBadPasswordCount $ sambaBadPasswordTime $ -> all of these are not set anymore in 1.0.9 unless samba tab is active. This means after activating samba one need to re-set the password.

ok

(from redmine: written on 2015-04-22)

By bmortier on 2017-09-02T15:14:49 (imported from GitLab)

In the adressbook of thundebrird, the title of a user does not appear. The field name in Thunderbird is the standard field "title"

Alex

(from redmine: written on 2015-04-23)

By Alex-31 on 2017-09-02T15:14:49 (imported from GitLab)

Removed non-standard academicTitle. Added standard title. personalTitle IS standard, it’s from cosine.schema but is only available in the weird pilotPerson objectClass. Should we use this objectClass? gosaDefaultLanguage marked as OBSOLETE Removed Samba stuff from gosaAccount, no reason for it to be there.

(from redmine: written on 2015-04-27)

By Côme Chilliet on 2017-09-02T15:14:49 (imported from GitLab)

hello,

applied to 1.0.9 and develop

Cheers

(from redmine: written on 2015-04-27)

By bmortier on 2017-09-02T15:14:50 (imported from GitLab)

hello,

yes we should use the pilotPerson objectClass if it not breaking something else

gosaLoginRestriction should be flagged obsolete and replace by fdLoginRestriction, its used by the restrcition based on ip adress to accept login on FD

for gender i don't know right now if its used or not ?? Cheers

(from redmine: written on 2015-04-27)

By bmortier on 2017-09-02T15:14:50 (imported from GitLab)

This patch adds pilotPerson. I changed the user filter to search for pilotPerson and inetOrgPerson. I sent a mail to the users mailing list to ask if anyone is using gender. For date of birth, maybe it could go in the personal plugin?