The filterProcessesUrl for the OIDCAuthenticationFilter is `openid_connect_login`

master
Christian Kleinbölting 2018-08-16 12:43:52 +02:00
parent 1c4f04ea97
commit 4eba4e58b6
1 changed files with 2 additions and 2 deletions

@ -20,7 +20,7 @@ The Principal object is an immutable map of the issuer and subject, a pairing wh
## Named administrator configuration ## 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: 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 # 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 ```xml
<bean id="openIdConnectAuthenticationFilter" class="org.mitre.openid.connect.client.OIDCAuthenticationFilter"> <bean id="openIdConnectAuthenticationFilter" class="org.mitre.openid.connect.client.OIDCAuthenticationFilter">