spring-projects / spring-projects/spring-security-samples
Problems with SAML2 samples
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 797
- Avg merge
- 3m
- Merged PRs (30d)
- 5
Description
I'm having problems trying to run these two SAML2 samples:
- https://github.com/spring-projects/spring-security-samples/tree/main/servlet/java-configuration/saml2/login
- https://github.com/spring-projects/spring-security-samples/tree/main/servlet/spring-boot/java/saml2/login
The Gradle command line in the READMEs doesn't work. I figured out what I think are the right tasks to invoke:
:servlet:java-configuration:saml2:login:appStartfor the first of the above samples, and:servlet:spring-boot:java:saml2:login:bootRunfor the second of the above samples.
For the first sample, Tomcat seems to come up but the webapp doesn't seem to be loaded. Going to http://localhost:8080 produces a generic Tomcat 404 page.
For the second sample, Tomcat and the webapp do come up. I'd like to be able to attach a debugger to it though and there doesn't seem to be a simple way to do that. (For the first sample, if it worked, I think I could use the ...:appStartDebug task to make it debuggable.)
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 with the READMEs in the two linked SAML2 sample directories and run the reported Gradle tasks: appStart and bootRun. Verify why the first sample serves Tomcat's 404 page and determine how the second sample can be started with debugger attachment. Done means the README commands work, the first webapp loads, and the second supports straightforward debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- authentication, build-system, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100