Skip to content

Commit 605469d

Browse files
vpavicjgrandja
authored andcommitted
Clarify default OAuth 2.0 login page requirements
Fixes gh-5996
1 parent 818a350 commit 605469d

File tree

1 file changed

+4
-0
lines changed
  • docs/manual/src/docs/asciidoc/_includes/servlet/additional-topics

1 file changed

+4
-0
lines changed

docs/manual/src/docs/asciidoc/_includes/servlet/additional-topics/oauth2.adoc

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,10 @@ The following sections go into more detail on each of the configuration options
9696
By default, the OAuth 2.0 Login Page is auto-generated by the `DefaultLoginPageGeneratingFilter`.
9797
The default login page shows each configured OAuth Client with its `ClientRegistration.clientName` as a link, which is capable of initiating the Authorization Request (or OAuth 2.0 Login).
9898

99+
[NOTE]
100+
In order for `DefaultLoginPageGeneratingFilter` to show links for configured OAuth Clients, the registered `ClientRegistrationRepository` needs to also implement `Iterable<ClientRegistration>`.
101+
See `InMemoryClientRegistrationRepository` for reference.
102+
99103
The link's destination for each OAuth Client defaults to the following:
100104

101105
`OAuth2AuthorizationRequestRedirectFilter.DEFAULT_AUTHORIZATION_REQUEST_BASE_URI` + "/{registrationId}"

0 commit comments

Comments
 (0)