spring-projects / spring-projects/spring-security
How to handle exceptions fired in CustomLdapAuthoritiesPopulator
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
Hi,
I am using spring security with Ldap. And I am using also CustomLdapAuthoritiesPopulator . For some reasons I have to fire some exceptions in the CustomLdapAuthoritiesPopulator. But unfortenatelly those exception could not be caught by the MVC Global Exception Handling: it is out of this scope.
My question so, is how can I handle those exception so that I can forward a proper error page to the end user.
Best Regards
HJ
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
The issue names CustomLdapAuthoritiesPopulator and MVC Global Exception Handling but no files or tests. Start by tracing how exceptions from the LDAP authorities population step move through Spring Security authentication, then compare that path with MVC exception handling. Done means documenting the supported handling path and how to present an appropriate error page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100