Assign Groups based on LDAP attributes #45

New issue

Open

opened 2022-10-21 18:07:43 +02:00 by magicfelix · 2 comments

magicfelix commented

2022-10-21 18:07:43 +02:00

(Migrated from edugit.org)

In Puavo, there are "roles" such as teacher, admin...

That LDAP attribute can be translated to AlekSIS groups by a user-configurable matching table.

In Puavo, there are "roles" such as teacher, admin... That LDAP attribute can be translated to AlekSIS groups by a user-configurable matching table.

magicfelix commented

2023-03-20 16:29:22 +01:00

(Migrated from edugit.org)

assigned to @magicfelix

magicfelix commented

2023-03-28 19:29:27 +02:00

(Migrated from edugit.org)

This is a similar principle to #46 , at least in the Puavo case, and should therefore be implemented in a re-usable way.

Both have in common, that the AlekSIS representation is an object (Person/Group) with a many-to-many or many-to-one relationship to another object (Group/GroupType), while the LDAP representation is an object (Person/Group) with an attribute that indicates group membership or type.

This is a similar principle to #46 , at least in the Puavo case, and should therefore be implemented in a re-usable way. Both have in common, that the AlekSIS representation is an object (Person/Group) with a many-to-many or many-to-one relationship to another object (Group/GroupType), while the LDAP representation is an object (Person/Group) with an attribute that indicates group membership or type.