123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324 |
- NOTE: Spring Security Reactive OAuth only supports authentication using a user info endpoint.
- Support for JWT validation will be added in https://github.com/spring-projects/spring-security/issues/5330[gh-5330].
- = OAuth 2.0 Login Sample
- This guide provides instructions on setting up the sample application with OAuth 2.0 Login using an OAuth 2.0 Provider or OpenID Connect 1.0 Provider.
- The sample application uses Spring Boot 2.0.0.M6 and the `spring-security-oauth2-client` module which is new in Spring Security 5.0.
- The following sections provide detailed steps for setting up OAuth 2.0 Login for these Providers:
- * <<google-login, Google>>
- * <<github-login, GitHub>>
- * <<facebook-login, Facebook>>
- * <<okta-login, Okta>>
- [[google-login]]
- == Login with Google
- This section shows how to configure the sample application using Google as the Authentication Provider and covers the following topics:
- * <<google-initial-setup,Initial setup>>
- * <<google-redirect-uri,Setting the redirect URI>>
- * <<google-application-config,Configure application.yml>>
- * <<google-boot-application,Boot up the application>>
- [[google-initial-setup]]
- === Initial setup
- To use Google's OAuth 2.0 authentication system for login, you must set up a project in the Google API Console to obtain OAuth 2.0 credentials.
- NOTE: https://developers.google.com/identity/protocols/OpenIDConnect[Google's OAuth 2.0 implementation] for authentication conforms to the
- https://openid.net/connect/[OpenID Connect 1.0] specification and is https://openid.net/certification/[OpenID Certified].
- Follow the instructions on the https://developers.google.com/identity/protocols/OpenIDConnect[OpenID Connect] page, starting in the section, "Setting up OAuth 2.0".
- After completing the "Obtain OAuth 2.0 credentials" instructions, you should have a new OAuth Client with credentials consisting of a Client ID and a Client Secret.
- [[google-redirect-uri]]
- === Setting the redirect URI
- The redirect URI is the path in the application that the end-user's user-agent is redirected back to after they have authenticated with Google
- and have granted access to the OAuth Client _(created in the previous step)_ on the Consent page.
- In the "Set a redirect URI" sub-section, ensure that the *Authorized redirect URIs* field is set to `http://localhost:8080/login/oauth2/code/google`.
- TIP: The default redirect URI template is `{baseUrl}/login/oauth2/code/{registrationId}`.
- The *_registrationId_* is a unique identifier for the `ClientRegistration`.
- IMPORTANT: If the application is running behind a proxy server, it is recommended to check https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#appendix-proxy-server[Proxy Server Configuration] to ensure the application is correctly configured.
- Also, see the supported https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#oauth2Client-auth-code-redirect-uri[`URI` template variables] for `redirect-uri`.
- [[google-application-config]]
- === Configure application.yml
- Now that you have a new OAuth Client with Google, you need to configure the application to use the OAuth Client for the _authentication flow_. To do so:
- . Go to `application.yml` and set the following configuration:
- +
- [source,yaml]
- ----
- spring:
- security:
- oauth2:
- client:
- registration: <1>
- google: <2>
- client-id: google-client-id
- client-secret: google-client-secret
- ----
- +
- .OAuth Client properties
- ====
- <1> `spring.security.oauth2.client.registration` is the base property prefix for OAuth Client properties.
- <2> Following the base property prefix is the ID for the `ClientRegistration`, such as google.
- ====
- . Replace the values in the `client-id` and `client-secret` property with the OAuth 2.0 credentials you created earlier.
- [[google-boot-application]]
- === Boot up the application
- Launch the Spring Boot 2.0 sample and go to `http://localhost:8080`.
- You are then redirected to the default _auto-generated_ login page, which displays a link for Google.
- Click on the Google link, and you are then redirected to Google for authentication.
- After authenticating with your Google account credentials, the next page presented to you is the Consent screen.
- The Consent screen asks you to either allow or deny access to the OAuth Client you created earlier.
- Click *Allow* to authorize the OAuth Client to access your email address and basic profile information.
- At this point, the OAuth Client retrieves your email address and basic profile information
- from the https://openid.net/specs/openid-connect-core-1_0.html#UserInfo[UserInfo Endpoint] and establishes an authenticated session.
- [[github-login]]
- == Login with GitHub
- This section shows how to configure the sample application using GitHub as the Authentication Provider and covers the following topics:
- * <<github-register-application,Register OAuth application>>
- * <<github-application-config,Configure application.yml>>
- * <<github-boot-application,Boot up the application>>
- [[github-register-application]]
- === Register OAuth application
- To use GitHub's OAuth 2.0 authentication system for login, you must https://github.com/settings/applications/new[Register a new OAuth application].
- When registering the OAuth application, ensure the *Authorization callback URL* is set to `http://localhost:8080/login/oauth2/code/github`.
- The Authorization callback URL (redirect URI) is the path in the application that the end-user's user-agent is redirected back to after they have authenticated with GitHub
- and have granted access to the OAuth application on the _Authorize application_ page.
- TIP: The default redirect URI template is `{baseUrl}/login/oauth2/code/{registrationId}`.
- The *_registrationId_* is a unique identifier for the `ClientRegistration`.
- IMPORTANT: If the application is running behind a proxy server, it is recommended to check https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#appendix-proxy-server[Proxy Server Configuration] to ensure the application is correctly configured.
- Also, see the supported https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#oauth2Client-auth-code-redirect-uri[`URI` template variables] for `redirect-uri`.
- [[github-application-config]]
- === Configure application.yml
- Now that you have a new OAuth application with GitHub, you need to configure the application to use the OAuth application for the _authentication flow_. To do so:
- . Go to `application.yml` and set the following configuration:
- +
- [source,yaml]
- ----
- spring:
- security:
- oauth2:
- client:
- registration: <1>
- github: <2>
- client-id: github-client-id
- client-secret: github-client-secret
- ----
- +
- .OAuth Client properties
- ====
- <1> `spring.security.oauth2.client.registration` is the base property prefix for OAuth Client properties.
- <2> Following the base property prefix is the ID for the `ClientRegistration`, such as github.
- ====
- . Replace the values in the `client-id` and `client-secret` property with the OAuth 2.0 credentials you created earlier.
- [[github-boot-application]]
- === Boot up the application
- Launch the Spring Boot 2.0 sample and go to `http://localhost:8080`.
- You are then redirected to the default _auto-generated_ login page, which displays a link for GitHub.
- Click on the GitHub link, and you are then redirected to GitHub for authentication.
- After authenticating with your GitHub credentials, the next page presented to you is "Authorize application".
- This page will ask you to *Authorize* the application you created in the previous step.
- Click _Authorize application_ to allow the OAuth application to access your personal user data information.
- At this point, the OAuth Client retrieves your personal user information
- from the UserInfo Endpoint and establishes an authenticated session.
- [TIP]
- For detailed information returned from the UserInfo Endpoint, see the API documentation
- for https://developer.github.com/v3/users/#get-the-authenticated-user["Get the authenticated user"].
- [[facebook-login]]
- == Login with Facebook
- This section shows how to configure the sample application using Facebook as the Authentication Provider and covers the following topics:
- * <<facebook-register-application,Add a New App>>
- * <<facebook-application-config,Configure application.yml>>
- * <<facebook-boot-application,Boot up the application>>
- [[facebook-register-application]]
- === Add a New App
- To use Facebook's OAuth 2.0 authentication system for login, you must first https://developers.facebook.com/apps[Add a New App].
- Select "Create a New App" and then the "Create a New App ID" page is presented. Enter the Display Name, Contact Email, Category and then click "Create App ID".
- NOTE: The selection for the _Category_ field is not relevant but it's a required field - select "Local".
- The next page presented is "Product Setup". Click the "Get Started" button for the *Facebook Login* product.
- In the left sidebar, under _Products -> Facebook Login_, select _Settings_.
- For the field *Valid OAuth redirect URIs*, enter `http://localhost:8080/login/oauth2/code/facebook` then click _Save Changes_.
- The OAuth redirect URI is the path in the application that the end-user's user-agent is redirected back to after they have authenticated with Facebook
- and have granted access to the application on the _Authorize application_ page.
- TIP: The default redirect URI template is `{baseUrl}/login/oauth2/code/{registrationId}`.
- The *_registrationId_* is a unique identifier for the `ClientRegistration`.
- IMPORTANT: If the application is running behind a proxy server, it is recommended to check https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#appendix-proxy-server[Proxy Server Configuration] to ensure the application is correctly configured.
- Also, see the supported https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#oauth2Client-auth-code-redirect-uri[`URI` template variables] for `redirect-uri`.
- [[facebook-application-config]]
- === Configure application.yml
- Now that you have created a new application with Facebook, you need to configure the sample application to use the application for the _authentication flow_. To do so:
- . Go to `application.yml` and set the following configuration:
- +
- [source,yaml]
- ----
- spring:
- security:
- oauth2:
- client:
- registration: <1>
- facebook: <2>
- client-id: facebook-client-id
- client-secret: facebook-client-secret
- ----
- +
- .OAuth Client properties
- ====
- <1> `spring.security.oauth2.client.registration` is the base property prefix for OAuth Client properties.
- <2> Following the base property prefix is the ID for the `ClientRegistration`, such as facebook.
- ====
- . Replace the values in the `client-id` and `client-secret` property with the OAuth 2.0 credentials you created earlier.
- [[facebook-boot-application]]
- === Boot up the application
- Launch the Spring Boot 2.0 sample and go to `http://localhost:8080`.
- You are then redirected to the default _auto-generated_ login page, which displays a link for Facebook.
- Click on the Facebook link, and you are then redirected to Facebook for authentication.
- After authenticating with your Facebook credentials, the next page presented to you is "Authorize application".
- This page will ask you to *Authorize* the application you created in the previous step.
- Click _Authorize application_ to allow the OAuth application to access your _public profile_ and _email address_ information.
- At this point, the OAuth Client retrieves your personal user information
- from the UserInfo Endpoint and establishes an authenticated session.
- [[okta-login]]
- == Login with Okta
- This section shows how to configure the sample application using Okta as the Authentication Provider and covers the following topics:
- * <<okta-register-application,Add Application>>
- * <<okta-assign-application-people,Assign Application to People>>
- * <<okta-application-config,Configure application.yml>>
- * <<okta-boot-application,Boot up the application>>
- [[okta-register-application]]
- === Add Application
- To use Okta's OAuth 2.0 authentication system for login, you must first https://www.okta.com/developer/signup[create a developer account].
- Sign in to your account sub-domain and navigate to _Applications -> Applications_ and then select the "Add Application" button.
- From the "Add Application" page, select the "Create New App" button and enter the following:
- * *Platform:* Web
- * *Sign on method:* OpenID Connect
- Select the _Create_ button.
- On the "General Settings" page, enter the Application Name (for example, "Spring Security Okta Login") and then select the _Next_ button.
- On the "Configure OpenID Connect" page, enter `http://localhost:8080/login/oauth2/code/okta` for the field *Redirect URIs* and then select _Finish_.
- The redirect URI is the path in the application that the end-user's user-agent is redirected back to after they have authenticated with Okta
- and have granted access to the application on the _Authorize application_ page.
- TIP: The default redirect URI template is `{baseUrl}/login/oauth2/code/{registrationId}`.
- The *_registrationId_* is a unique identifier for the `ClientRegistration`.
- IMPORTANT: If the application is running behind a proxy server, it is recommended to check https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#appendix-proxy-server[Proxy Server Configuration] to ensure the application is correctly configured.
- Also, see the supported https://docs.spring.io/spring-security/site/docs/current/reference/htmlsingle/#oauth2Client-auth-code-redirect-uri[`URI` template variables] for `redirect-uri`.
- [[okta-assign-application-people]]
- === Assign Application to People
- From the "General" tab of the application, select the "Assignments" tab and then select the _Assign_ button.
- Select _Assign to People_ and assign your account to the application. Then select the _Save and Go Back_ button.
- [[okta-application-config]]
- === Configure application.yml
- Now that you have created a new application with Okta, you need to configure the sample application to use the application for the _authentication flow_. To do so:
- . Go to `application.yml` and set the following configuration:
- +
- [source,yaml]
- ----
- spring:
- security:
- oauth2:
- client:
- registration: <1>
- okta: <2>
- client-id: okta-client-id
- client-secret: okta-client-secret
- provider: <3>
- okta:
- authorization-uri: https://your-subdomain.oktapreview.com/oauth2/v1/authorize
- token-uri: https://your-subdomain.oktapreview.com/oauth2/v1/token
- user-info-uri: https://your-subdomain.oktapreview.com/oauth2/v1/userinfo
- user-name-attribute: sub
- jwk-set-uri: https://your-subdomain.oktapreview.com/oauth2/v1/keys
- ----
- +
- .OAuth Client properties
- ====
- <1> `spring.security.oauth2.client.registration` is the base property prefix for OAuth Client properties.
- <2> Following the base property prefix is the ID for the `ClientRegistration`, such as okta.
- <3> `spring.security.oauth2.client.provider` is the base property prefix for OAuth Provider properties.
- ====
- . Replace the values in the `client-id` and `client-secret` property with the OAuth 2.0 credentials you created earlier.
- As well, replace `https://your-subdomain.oktapreview.com` in `authorization-uri`, `token-uri`, `user-info-uri` and `jwk-set-uri` with the sub-domain assigned to your account during the registration process.
- [[okta-boot-application]]
- === Boot up the application
- Launch the Spring Boot 2.0 sample and go to `http://localhost:8080`.
- You are then redirected to the default _auto-generated_ login page, which displays a link for Okta.
- Click on the Okta link, and you are then redirected to Okta for authentication.
- After authenticating with your Okta account credentials, the OAuth Client retrieves your email address and basic profile information
- from the https://openid.net/specs/openid-connect-core-1_0.html#UserInfo[UserInfo Endpoint] and establishes an authenticated session.
|