On Sun, Dec 24, 2017 at 2:57 AM, Mayank Gupta wrote:
> Hello everyone,
Hi Mayank,
> I'm Mayank Gupta, I successfully completed a project under CCExtractor
> organisation in Google Summer of Code 2017, I am interested in developing
> "New Season of KDE webste" under Season of KDE 2018. From @baloneyGeek I got
> to know KDE Identity uses standard LDAP userdb and also that I'd need to
> setup dummy server for the same to test KDE identity integration for
> developed website.
>
> So about the implementation of idea 'New SoK website', when integrating KDE
> Identity (which uses LDAP db), do the 'Org Admins' belong to different
> `OrganisationalUnit` on the server? or do they have some different set of
> attribute(s) which could enable business logic to identify their 'KDE
> Identity' as 'admin' and different from that of mentors and students?
All users, whether students, developers, sysadmins or other members of
the community are stored in the same organisational unit.
Our directory has a 'groupMember' attribute which can be used to
determine the groups a user is part of, so i'd suggest referring to
that.
When creating this I would advise structuring it in such a way that
LDAP could be replaced by another protocol, such as a HTTP API
(authenticated using OAuth) in the future.
>
> Also, if possible, could anyone provide with a crude schema of db so that it
> gets easy to write LDAP queries in website and also setting up the dummy
> database, which would indeed ease the process of unplugging the dummy LDAP
> db and plugging in the real one.
You can find the schemas we have loaded in our directory at
https://cgit.kde.org/websites/identity-kde-org.git/tree/protected/data/
This is in addition to the standard LDAP objectClasses of course.
Please let me know if you have any questions about the specific data
which might be stored for a user.
>
> Thanks,
> Mayank Gupta
Cheers,
Ben Cooksley
KDE Sysadmin
