
------------------------------------------------------------------
== The relying party drives the flow   [confidential client, no PKCE - the Boot default]
------------------------------------------------------------------
GET http://127.0.0.1:8080/orders while unauthenticated. Every hop below is a real redirect.

  302  http://127.0.0.1:8080/orders
  302  http://127.0.0.1:8080/oauth2/authorization/demo-web
  302  http://localhost:9000/oauth2/authorize?response_type=code&client_id=demo-web&scope=orders.write%20openid%20profile%20orders.read&state=ONw1L2XOM3BG7j5kgeISWex_263H9-sYOJeG5lcrGv8%3D&redirect_uri=http://127.0.0.1:8080/login/oauth2/code/demo-web&nonce=VSauV4DIo1T-zZKYq8as0fEwQjqmhx462L3sCCBnAHk
  302  http://127.0.0.1:8080/login/oauth2/code/demo-web?error=invalid_request&error_description=OAuth%202.0%20Parameter%3A%20code_challenge&error_uri=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Frfc7636%23section-4.4.1&state=ONw1L2XOM3BG7j5kgeISWex_263H9-sYOJeG5lcrGv8%3D
  200  http://127.0.0.1:8080/login?error

The authorization request the client built:
    http://localhost:9000/oauth2/authorize
    response_type=code
    client_id=demo-web
    scope=orders.write%20openid%20profile%20orders.read
    state=ONw1L2XOM3BG7j5kgeISWex_263H9-sYOJeG5lcrGv8%3D
    redirect_uri=http://127.0.0.1:8080/login/oauth2/code/demo-web
    nonce=VSauV4DIo1T-zZKYq8as0fEwQjqmhx462L3sCCBnAHk
    >>> NO code_challenge - a client registered with
    >>> requireProofKey(true) will reject this outright

The flow ended at the CLIENT's error page, not the provider's. The provider
rejected the authorization request and redirected the failure back to the
registered redirect_uri, so nothing in the client's logs names the provider
as the cause. The reason is only in the query string above.

------------------------------------------------------------------
== What the client rendered
------------------------------------------------------------------
Please sign in
Login with OAuth 2.0
Invalid credentials
http://localhost:9000
