[Invitations] - Problem with public form not installed as well as sendmail. Review required on acceptation / refusal.
[Invitations] - Problem with public form not installed as well as sendmail. Review required on acceptation / refusal.
[Invitations] - Review required on acceptation / refusal.
Potential issues :
- The acceptation is actually obsolete, the user is directly created at root (by default).
- Only the refusal of the registration makes the user being removed.
It could be interesting to move the user not accepted within a special ou and maybe with a lock status. (see impact on supannAccountStatus).
To be discussed and re-designed properly.
Activity
changed milestone to %FusionDirectory 1.5
added PJ1802-0188 label
assigned to @tdockx
added enhancement plugin-invitations labels
Hello @tdockx
moved the part about the packaging to a packaging issues
changed milestone to %FusionDirectory 1.6
I'm experiencing the same issues.
In my case, I want to be able to delegate the management of LDAP groups to those responsible, which means they also have to be able to request new LDAP groups for new projects and applications. I thought the invitations plugin would meet those requirements but I faced several issues.
I configured apache php.ini to use msmtp for sending mails and it works. But the problem is the invitation sent is one-time use only. It means each time someone wants to create a group they'd have to ask me for an invitation.
The second problem I encountered is what you pointed out in this issue : the group is actually created until I see it and decide to remove it or not. It would be great to have a "pending" ou, and once approved from the registration, move the object in the appropriate ou (people ou for users, groups ou for groups, ...)
mentioned in issue #6324 (closed)
hello @mluongo
- yes this part will be rewritten in our new orchestration framework, FusionDirectory ORchestrator
- there was code to do that, but it was specific to a customer.
Cheers
