LDAP user sync
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 845
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Description
Right now iris-sync-targets only supports syncing mailing lists / groups from LDAP.
For many use cases, it does not make sense to use oncall, and instead use LDAP for users. This is so it is easy to setup target user, or for iris-relay to know about the user (i.e. from slack).
I would like to work on this, for our setup (we do not use oncall at the moment, because we instead route alerts to various shared slack channels, not persons; and we do have a lot of time specific requirements, i.e. weekdays/weekends, working hours/non-working hours), but any input from other users and maintainers, would be useful. I am committed to implementing this.
I think it should be synced from ldap to mysql periodically, so even if ldap is down or unreachable, full alerting / escalation stack works.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing iris-sync-targets LDAP group and mailing-list synchronization path. Then determine how LDAP users should be represented in MySQL and how periodic syncing should behave when LDAP is unavailable. Done means the requirements, storage model, synchronization behavior, and failure handling are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100