From 4eba4e58b698f1576602dc4fad0b60296ee02eb0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20Kleinb=C3=B6lting?= Date: Thu, 16 Aug 2018 12:43:52 +0200 Subject: [PATCH] The filterProcessesUrl for the OIDCAuthenticationFilter is `openid_connect_login` --- Client-configuration.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Client-configuration.md b/Client-configuration.md index 1d523bb..eebb102 100644 --- a/Client-configuration.md +++ b/Client-configuration.md @@ -20,7 +20,7 @@ The Principal object is an immutable map of the issuer and subject, a pairing wh ## Named administrator configuration -By default all valid users get a special Spring Security GrantedAuthority that is based on the issuer and subject of the user, such as `OIDC_2398ufe23u_https://example-idp.com/openid-connect-server/`. +By default all valid users get a special Spring Security GrantedAuthority that is based on the issuer and subject of the user, such as `OIDC_2398ufe23u_https://example-idp.com/openid_connect_login/`. To map these authorities into more useful ones like **ROLE_USER** and **ROLE_ADMIN**, you need to wire in an authorities mapper, such as the one included in the client library: @@ -42,7 +42,7 @@ To map these authorities into more useful ones like **ROLE_USER** and **ROLE_ADM # Filter -There is one filter class `org.mitre.openid.connect.client.OIDCAuthenticationFilter` that handles all core client (or "Relying Party") functions. It is set to listen on `/openid-connect-login` at the root of the application. The filter bean is configured like this: +There is one filter class `org.mitre.openid.connect.client.OIDCAuthenticationFilter` that handles all core client (or "Relying Party") functions. It is set to listen on `/openid_connect_login` at the root of the application. The filter bean is configured like this: ```xml