Event Listener API for phpCAS 2.0
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 798
- Forks
- 419
- PR merge metrics
- No merged PRs in 30d
Description
Description
An event-listener API could simplify the CAS client implementation by allowing modules to execute their own code at various points during the authentication sequence. In contrast, the phpCAS 1.x code has this sequence-dependent code injected into the various authentication functions.
This feature was first discussed and outlined in this comment on PHPCAS-100: https://issues.jasig.org/browse/PHPCAS-100?focusedCommentId=23404&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-23404
Contributor guide
No contributing guide indexed for this repository
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 reading the migrated PHPCAS-119 description and the referenced PHPCAS-100 discussion. Trace the phpCAS 1.x authentication functions and their sequence-dependent code to understand the existing flow. Done means defining and implementing an event-listener API that lets modules execute code at documented points during authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100