MOD-42: Syncing Users to Modulus

[elliott (Elliott Williams)]

@burke

If the owner string matched an OpenMRS ID, it would display as the user; otherwise, it would display as a free text string. Filling out the owner field could show choices that match known names & IDs of the community, but would allow for any free text value. Picking a user from the choice list would just facilitate setting the field to their OpenMRS ID.

My only concern with this is that then we can’t really delegate permissions to the owner. It would be more of a cosmetic value.

However I just looked back to Authorization in Modulus and it sounds like that was the consensus we arrived at! In that case, I’ll switch what I had in my code.

Authorization in Modulus

Historically, we have had a single “owner” of any given module. While I think it’s good to identify an owner, it would be nice if more than one person could be designated to edit a module’s entry in the repository. For example, the person overseeing or doing most of the work on a module might want to designate one or more person(s) who can upload new versions or edit metadata about the module on their behalf. Is there any documentation about the planned authorization model for modulus at this…

---

@burke

Are you saying that Modulus can’t search the list of known OpenMRS users (names & OpenMRS IDs)?

Yes. Unless we write an ID Dashboard search API, or we teach Modulus to access LDAP, there’s no way to search for users who have never logged in to Modulus.

FWIW, Atlassian apps sync there user databases with Crowd to alleviate this. Syncing with LDAP periodically would be a similar approach.