Skip to content
This repository has been archived by the owner on May 2, 2018. It is now read-only.

LDAP sync incomplete #38

Open
kohlhase opened this issue Sep 9, 2014 · 6 comments
Open

LDAP sync incomplete #38

kohlhase opened this issue Sep 9, 2014 · 6 comments

Comments

@kohlhase
Copy link

kohlhase commented Sep 9, 2014

I have synced the GenCS students via https://panta.kwarc.info/ldap-course-sync/664, but I only get 44 students in https://panta.kwarc.info/group/node/664/admin/people?state=All&uid=&page=1. But it should be 53+me+3TAs=57.
I am not sure what happened, could you have a look? I need to resolve this urgently.

@kohlhase
Copy link
Author

kohlhase commented Sep 9, 2014

The same problem is with the GenICT 2014 course, only in a much more drastic way.

@nickles-lee
Copy link

I recall Dominik and Tom having issues getting their OpenJUB API to successfully sync LDAP entries from Jacobs Servers.

Commit that apparently fixed things: https://github.com/tkw1536/openjub-api/commit/142dc9c61a1ca198962a5e91a5fdf275760677cd
Discussion of the bug: OpenJUB/openjub-api-legacy#4

This might be a similar problem

@mihaifieraru
Copy link
Contributor

Only students whose registrations are accepted via CampusNet are going to LDAP and then to Panta.
Are all the 53 students accepted in the course on CampusNet?

@kohlhase
Copy link
Author

kohlhase commented Sep 9, 2014

yes, they are, and moreover, they show up in jgrader, so they must be in the LDAP.

@mihaifieraru
Copy link
Contributor

The reason why the students don't appear in the LDAP list is because they have never logged in on panta.kwarc.info, so their account does not exist. Once they log in with CAMPUSNET credentials, their account will be generated and the system will add them to the list of accounts to be sync.

This is not a very good design :(

@tkw1536
Copy link
Contributor

tkw1536 commented Sep 13, 2014

@fierarufmihai You should just have a login-as feature (masquerade as LDAP-user) for admin(s). It is what I ended up doing that for the USG forum. It just needs SOME credentials to access LDAP. It can just grab the data from someone else then. Yes, it is hacky, but it will work.

@nickles-lee The LDAP syncing problems resulted from too many simultanious LDAP connections (was copying everything async to the local DB).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants