spring-projects / spring-projects/spring-ldap
Listening for change
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 375
- Forks
- 501
- Avg merge
- 6h 4m
- Merged PRs (30d)
- 63
Description
Hey, is there any easy way to listen for changes on objectClass = group for example ?
The idea is that, for example, if the memberIds in a group changes then the logged-in LDAP user in the spring application should be informed that something has changed.
Similarly can be used in listening for password changes, if changed then blacklist related refreshToken.
I currently have this done on @Scheduled() and check every 60 seconds.
I wonder if it can be done better to make it work in real time.
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 reviewing the existing @Scheduled() polling approach and how changes to LDAP objectClass = group, memberIds, and passwords are observed. Define the desired real-time notification behavior for logged-in users and refreshToken invalidation before identifying the appropriate project entry points and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100