Skip to content
GitLab
Closed
Issue created by dockx thibault@tdockxDeveloper

[Partage-Renater] - getAccount method - Proper account updates

Requirements

It seems an issue might exist making the getAccount method logic not efficient.

An adaptation of the method is therefore required in order to :

  • Verify if the account exists on the Partage side and create it with proper attributes if not.
  • Verify if the account exists on the Partage side and modify with proper attributes values if yes.

A complete re-design of the logic has been worked on. Details below:

User has no mail tab active

  • creation of mailbox
  • Verification if Partage has an entry already.
    • IF backend configuration says, LDAP is always right. Update the Partage attributes value with LDAP values.
      • IF the Partage account is reported as something else than ACTIVE
        • If backend configuration report to re-active account if not active, Re-activate account and update values
        • Else : Error message, account is [status]
    • ELSE issue an error message "Already exist".

If user as mail tab active

  • Verification of account exists on Partage and is active.
  • If not active -> Error message saying to reactivate the account.

Careful that no emails ca be changed on Update !

New Features
New mail account status within User, Mail Tab

zimbraAccountStatus
    String(active, closed, locked, lockout, pending, maintenance).

Backend config tab renater partage

  • Re-activate account if already exist during mailbox creation.
  • Trust LDAP and push LDAP Attributes values to Partage. Overriding.
  • Removal of tab Mail within User: Delete / Lock.

Descriptive title for this enhancement

[Partage-Renater] - getAccount method - Proper account updates

Actual behavior

It is has been reported that the update on Partage side is not performed properly.

Expected behavior

Proper updates taking the information from the LDAP source as truthful, therefore updating Partage properly.

Step by step description of new behaviour

The getAccount method will update or create the account properly.

Benefits

A better replication of the LDAP information to harmonize the data.

Possible Drawbacks

LDAP is considered the one having the latest and proper information, therefore pushing its data. If Partage contains different attributes values than LDAP they will be updated.

Applicable Issues

None.

Edited by dockx thibault