Configuração de um cliente OAuth2
Configure sua aplicação para atuar como um cliente OAuth2, definindo os detalhes de registro para vários provedores.
Configuração de um cliente OAuth2 é uma aula grátis de Spring Security 6 & JWT Authentication no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Spring Security 6 & JWT Authentication, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Spring Security 6 & JWT Authentication inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
What is an OAuth2 Client?
In OAuth2, an OAuth2 Client is an application that wants to access resources on behalf of a user from a Resource Server. Think of it as your app asking permission to use another service (like Google or GitHub) on your behalf.
It's not the user, but an application acting for the user.
Why Configure Our App?
To use an external service's API (e.g., getting user profiles, posting updates), your application needs to be recognized by that service. This recognition process is called client registration.
- Your app gets a unique identity.
- The service knows who is requesting access.
- It enables secure communication and authorization.
Key Client Registration Details
When you register your application with an OAuth2 Authorization Server (the service that grants access), you'll typically provide and receive:
- Client ID: A public identifier for your application.
- Client Secret: A confidential key used to authenticate your app.
- Redirect URI(s): Where the Authorization Server sends the user back after authorization.
Spring Security as an OAuth2 Client
Spring Security makes it incredibly easy to configure your Spring Boot application to act as an OAuth2 Client. It handles much of the complex OAuth2 flow automatically.
All you need to do is provide the necessary registration details for the external service you want to connect to.
Client Configuration File
Spring Security's OAuth2 client configuration lives primarily in your application.yml or application.properties file.
You'll use two main prefixes:
spring.security.oauth2.client.registration: Defines details about your app's registration with a specific provider.spring.security.oauth2.client.provider: Defines details about the OAuth2 provider itself (e.g., its authorization endpoint).
Setting Up a Provider
Under spring.security.oauth2.client.provider.[provider-name], you define the endpoints of the external OAuth2 service. For example, for a provider named github:
authorization-uri: Where users go to authorize your app.token-uri: Where your app exchanges codes for tokens.user-info-uri: Where your app fetches user details.
Often, Spring Boot can auto-configure these for popular providers if you just provide the client-id and client-secret.
Registering Your Client App
Under spring.security.oauth2.client.registration.[registration-id], you specify your app's unique registration details for a given provider. The registration-id acts as a unique name for your specific client configuration.
provider: Links to a defined provider (e.g.,github).client-id: Your app's public ID.client-secret: Your app's secret key.redirect-uri: The callback URL.scope: Permissions your app requests (e.g.,read:user).authorization-grant-type: The OAuth2 flow used (e.g.,authorization_code).
Example: GitHub Client Setup
Let's look at a concrete example using GitHub. You would first register your application on GitHub's developer settings to get a Client ID and Client Secret.
Then, configure your application.yml:
spring:
security:
oauth2:
client:
registration:
github:
client-id: your-github-client-id
client-secret: your-github-client-secret
redirect-uri: "{baseUrl}/login/oauth2/code/{registrationId}"
scope: read:user,user:email
provider:
github:
authorization-uri: https://github.com/login/oauth/authorize
token-uri: https://github.com/login/oauth/access_token
user-info-uri: https://api.github.com/userMinimal Spring Boot App
To enable OAuth2 client functionality, ensure you have the spring-boot-starter-oauth2-client dependency. Spring Boot will automatically detect the configuration and set up the necessary filters.
Here's a basic Spring Boot application entry point:
package com.coddykit;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
import java.security.Principal;
@SpringBootApplication
@RestController
public class Oauth2ClientApp {
public static void main(String[] args) {
SpringApplication.run(Oauth2ClientApp.class, args);
}
@GetMapping("/")
public String welcome(Principal principal) {
if (principal != null) {
return "Hello, " + principal.getName() + "! You are logged in with OAuth2.";
}
return "Hello! Please log in with OAuth2.";
}
}The Automated OAuth2 Flow
Once configured, Spring Security automatically:
- Redirects unauthenticated users to the configured Authorization Server's login page.
- Handles the authorization code exchange after the user grants permission.
- Fetches user details from the
user-info-uri. - Populates the
SecurityContextwith the authenticated user.
This significantly simplifies implementing OAuth2 client logic.
Quick Check: Client Config
You're setting up a Spring Boot application to act as an OAuth2 client for an external service. Which of the following properties is primarily used to identify your application to the external service, and should be kept confidential?
Recap: OAuth2 Client Setup
You've learned how to configure your Spring Boot application as an OAuth2 Client. We covered:
- The role of an OAuth2 Client.
- Key configuration properties like
client-idandclient-secret. - How to use
application.ymlfor client and provider registration. - Spring Security's automatic handling of the OAuth2 flow.
Next, we'll dive into integrating specific social login providers like Google and GitHub in more detail!
Perguntas Frequentes
A aula “Configuração de um cliente OAuth2” é grátis?
Sim — o texto completo de “Configuração de um cliente OAuth2” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Spring Security 6 & JWT Authentication, atualize para CoddyKit PRO. O curso de Spring Security 6 & JWT Authentication inclui 4 aulas no total.
O que vou aprender em “Configuração de um cliente OAuth2”?
Configure sua aplicação para atuar como um cliente OAuth2, definindo os detalhes de registro para vários provedores. Você pratica Spring Security 6 & JWT Authentication com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Spring Security 6 & JWT Authentication?
Nenhuma experiência prévia é necessária. Spring Security 6 & JWT Authentication no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.
Quanto tempo leva a aula “Configuração de um cliente OAuth2”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Spring Security 6 & JWT Authentication?
Sim. Cada aula de Spring Security 6 & JWT Authentication inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Configuração de um cliente OAuth2
- Integração de login social
- Manipulador personalizado de sucesso do OAuth2
- Acessando o usuário OAuth2 autenticado