apollographql / apollographql/subgraph-template-java-spring-graphql-boilerplate
Add Spring Security
- Dominant language
- Java
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We're using a simple mentod for router auth and CORS headers, but we want to switch to Spring Security to set up consumers for success long term. This means, in `Application.java`:
```[tasklist]
- [ ] Replace `addInterceptors` (and the associated `RouterInterceptor`) with a comparable Spring Security config. It should _always_ require Router auth (even if the user is authenticated by other means) and, ideally, allow that requirement to be disabled for local development.
- [ ] Replace `addCorsMappings` usage with Spring Security CORS settings with comparable rules (accessible from Studio, credentials allowed, all headers allowed)
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in Application.java by reading the existing addInterceptors and addCorsMappings configuration, then inspect the associated RouterInterceptor. Compare those current authentication and CORS rules with the tasklist requirements, including local-development behavior, and verify that the resulting configuration preserves the stated access, credentials, and header behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- authentication, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100