Ankur Mhatre
38c0a5f358
Three modules on Spring Boot 4.1.1 with Spring Authorization Server 7.1.1: the provider
itself, a relying party, and an API that trusts its tokens. Client registration, PKCE,
a custom consent page and token customisation, with profiles that make each failure
reproducible.
Every claim is backed by captured output in docs/output/as-*.txt, regenerated by
authorization-server/scripts/run-all.sh. Notable findings, verified against the jars:
- OAuth2AuthorizationServerConfiguration.applyDefaultSecurity(HttpSecurity) was deleted
in 7.0, and both configuration classes moved into spring-security-config
- ClientSettings.requireProofKey flipped from false to true, on the authorization server
(1.5.8 -> 7.1.1) and on the OAuth2 client (6.5.1 -> 7.1.1)
- requireProofKey(false) does not make PKCE optional for a public client; the code
verifier is that client's only authentication at the token endpoint
- MediaTypeRequestMatcher(TEXT_HTML) matches Accept: */*, so the token endpoint answers
API callers with 302 -> /login unless setIgnoredMediaTypes(ALL) is called
Also renames the repository to spring-auth-demo and cross-links the new chapter set from
the existing documentation.
33 lines
1.5 KiB
Plaintext
33 lines
1.5 KiB
Plaintext
|
|
------------------------------------------------------------------
|
|
== A token for a DIFFERENT audience, signed by the SAME issuer
|
|
------------------------------------------------------------------
|
|
demo-service's tokens carry aud=[orders-api] thanks to the token customiser.
|
|
Here we ask for one and then present it to a resource server configured to
|
|
require a different audience - and to one that does not check at all.
|
|
|
|
aud claim in the token:
|
|
"aud": "orders-api",
|
|
"exp": 1787539386,
|
|
"iat": 1787538786,
|
|
"iss": "http://localhost:9000",
|
|
|
|
------------------------------------------------------------------
|
|
== Resource server running with demo.validate-audience=false
|
|
------------------------------------------------------------------
|
|
This is the Spring Boot default: issuer-uri alone validates signature, exp/nbf
|
|
and iss. Audience is not checked unless you add a validator.
|
|
GET /api/orders -> 200
|
|
{"orders":[{"total":"42.00","id":1}],"subject":"demo-service","clientId":null,"scopes":["orders.read"],"roles":null,"tenant":"acme","audience":["orders-api"]}
|
|
|
|
------------------------------------------------------------------
|
|
== The same token with a deliberately mangled signature
|
|
------------------------------------------------------------------
|
|
HTTP/1.1 200
|
|
|
|
------------------------------------------------------------------
|
|
== No token at all
|
|
------------------------------------------------------------------
|
|
HTTP/1.1 401
|
|
WWW-Authenticate: Bearer resource_metadata="http://localhost:8090/.well-known/oauth-protected-resource"
|