2017-03-31 153 views
0

是否有人成功配置了以ADFS作为身份提供者的Spring Boot OAuth2?我成功地在Facebook上跟随了本教程,https://spring.io/guides/tutorials/spring-boot-oauth2/,但ADFS似乎没有userInfoUri。我认为ADFS会在令牌本身(JWT格式?)中返回声明数据,但不确定如何使其与Spring一起工作。这是我迄今在我的属性文件中:如何为ADFS配置spring引导安全OAuth2?

security: 
    oauth2: 
    client: 
     clientId: [client id setup with ADFS] 
     userAuthorizationUri: https://[adfs domain]/adfs/oauth2/authorize?resource=[MyRelyingPartyTrust] 
     accessTokenUri: https://[adfs domain]/adfs/oauth2/token 
     tokenName: code 
     authenticationScheme: query 
     clientAuthenticationScheme: form 
     grant-type: authorization_code 
    resource: 
     userInfoUri: [not sure what to put here?] 

回答

3

tldr; ADFS将用户信息嵌入oauth标记中。您需要创建并重写org.springframework.boot.autoconfigure.security.oauth2.resource.UserInfoTokenServices对象提取这些信息,并把它添加到Principal对象

要开始,首先按照春的OAuth2教程https://spring.io/guides/tutorials/spring-boot-oauth2/。使用这些应用程序属性(在自己的域名填写):

security: 
    oauth2: 
    client: 
     clientId: [client id setup with ADFS] 
     userAuthorizationUri: https://[adfs domain]/adfs/oauth2/authorize?resource=[MyRelyingPartyTrust] 
     accessTokenUri: https://[adfs domain]/adfs/oauth2/token 
     tokenName: code 
     authenticationScheme: query 
     clientAuthenticationScheme: form 
     grant-type: authorization_code 
    resource: 
     userInfoUri: https://[adfs domain]/adfs/oauth2/token 

注意:我们将忽略无论是在userInfoUri,但春天的OAuth2似乎需要的东西在那里。

创建一个新类,AdfsUserInfoTokenServices,您可以在下面复制和调整(您将需要清理一些)。这是Spring类的副本;如果你愿意,你可以大概延长了,但我做了足够的变化,其中似乎没有像它我得到许多:

package edu.bowdoin.oath2sample; 

import java.util.Base64; 
import java.util.Collections; 
import java.util.List; 
import java.util.Map; 

import org.slf4j.Logger; 
import org.slf4j.LoggerFactory; 
import org.springframework.boot.autoconfigure.security.oauth2.resource.AuthoritiesExtractor; 
import org.springframework.boot.autoconfigure.security.oauth2.resource.FixedAuthoritiesExtractor; 
import org.springframework.boot.autoconfigure.security.oauth2.resource.FixedPrincipalExtractor; 
import org.springframework.boot.autoconfigure.security.oauth2.resource.PrincipalExtractor; 
import org.springframework.security.authentication.UsernamePasswordAuthenticationToken; 
import org.springframework.security.core.AuthenticationException; 
import org.springframework.security.core.GrantedAuthority; 
import org.springframework.security.oauth2.client.OAuth2RestOperations; 
import org.springframework.security.oauth2.common.DefaultOAuth2AccessToken; 
import org.springframework.security.oauth2.common.OAuth2AccessToken; 
import org.springframework.security.oauth2.common.exceptions.InvalidTokenException; 
import org.springframework.security.oauth2.provider.OAuth2Authentication; 
import org.springframework.security.oauth2.provider.OAuth2Request; 
import org.springframework.security.oauth2.provider.token.ResourceServerTokenServices; 
import org.springframework.util.Assert; 

import com.fasterxml.jackson.core.type.TypeReference; 
import com.fasterxml.jackson.databind.ObjectMapper; 

public class AdfsUserInfoTokenServices implements ResourceServerTokenServices { 

protected final Logger logger = LoggerFactory.getLogger(getClass()); 

private final String userInfoEndpointUrl; 

private final String clientId; 

private String tokenType = DefaultOAuth2AccessToken.BEARER_TYPE; 

private AuthoritiesExtractor authoritiesExtractor = new FixedAuthoritiesExtractor(); 

private PrincipalExtractor principalExtractor = new FixedPrincipalExtractor(); 

public AdfsUserInfoTokenServices(String userInfoEndpointUrl, String clientId) { 
    this.userInfoEndpointUrl = userInfoEndpointUrl; 
    this.clientId = clientId; 
} 

public void setTokenType(String tokenType) { 
    this.tokenType = tokenType; 
} 

public void setRestTemplate(OAuth2RestOperations restTemplate) { 
    // not used 
} 

public void setAuthoritiesExtractor(AuthoritiesExtractor authoritiesExtractor) { 
    Assert.notNull(authoritiesExtractor, "AuthoritiesExtractor must not be null"); 
    this.authoritiesExtractor = authoritiesExtractor; 
} 

public void setPrincipalExtractor(PrincipalExtractor principalExtractor) { 
    Assert.notNull(principalExtractor, "PrincipalExtractor must not be null"); 
    this.principalExtractor = principalExtractor; 
} 

@Override 
public OAuth2Authentication loadAuthentication(String accessToken) 
     throws AuthenticationException, InvalidTokenException { 
    Map<String, Object> map = getMap(this.userInfoEndpointUrl, accessToken); 
    if (map.containsKey("error")) { 
     if (this.logger.isDebugEnabled()) { 
      this.logger.debug("userinfo returned error: " + map.get("error")); 
     } 
     throw new InvalidTokenException(accessToken); 
    } 
    return extractAuthentication(map); 
} 

private OAuth2Authentication extractAuthentication(Map<String, Object> map) { 
    Object principal = getPrincipal(map); 
    List<GrantedAuthority> authorities = this.authoritiesExtractor 
      .extractAuthorities(map); 
    OAuth2Request request = new OAuth2Request(null, this.clientId, null, true, null, 
      null, null, null, null); 
    UsernamePasswordAuthenticationToken token = new UsernamePasswordAuthenticationToken(
      principal, "N/A", authorities); 
    token.setDetails(map); 
    return new OAuth2Authentication(request, token); 
} 

/** 
* Return the principal that should be used for the token. The default implementation 
* delegates to the {@link PrincipalExtractor}. 
* @param map the source map 
* @return the principal or {@literal "unknown"} 
*/ 
protected Object getPrincipal(Map<String, Object> map) { 
    Object principal = this.principalExtractor.extractPrincipal(map); 
    return (principal == null ? "unknown" : principal); 
} 

@Override 
public OAuth2AccessToken readAccessToken(String accessToken) { 
    throw new UnsupportedOperationException("Not supported: read access token"); 
} 

private Map<String, Object> getMap(String path, String accessToken) { 
    if (this.logger.isDebugEnabled()) { 
     this.logger.debug("Getting user info from: " + path); 
    } 
    try { 
     DefaultOAuth2AccessToken token = new DefaultOAuth2AccessToken(
       accessToken); 
     token.setTokenType(this.tokenType); 

     logger.debug("Token value: " + token.getValue()); 

     String jwtBase64 = token.getValue().split("\\.")[1]; 

     logger.debug("Token: Encoded JWT: " + jwtBase64); 
     logger.debug("Decode: " + Base64.getDecoder().decode(jwtBase64.getBytes())); 

     String jwtJson = new String(Base64.getDecoder().decode(jwtBase64.getBytes())); 

     ObjectMapper mapper = new ObjectMapper(); 

     return mapper.readValue(jwtJson, new TypeReference<Map<String, Object>>(){}); 
    } 
    catch (Exception ex) { 
     this.logger.warn("Could not fetch user details: " + ex.getClass() + ", " 
       + ex.getMessage()); 
     return Collections.<String, Object>singletonMap("error", 
       "Could not fetch user details"); 
    } 
} 
} 

的GetMap操作方法,其中令牌值进行分析,而JWT格式的用户信息是提取和解码(错误检查可以在这里得到改进,这是一个粗略的草案,但给你的要点)。见朝着这个链接的信息,对ADFS如何令牌中嵌入数据底部:https://blogs.technet.microsoft.com/askpfeplat/2014/11/02/adfs-deep-dive-comparing-ws-fed-saml-and-oauth/

添加到您的配置:

@Autowired 
private ResourceServerProperties sso; 

@Bean 
public ResourceServerTokenServices userInfoTokenServices() { 
    return new AdfsUserInfoTokenServices(sso.getUserInfoUri(), sso.getClientId()); 
} 

现在按照这些指令设置的第一部分ADFS客户端和依赖方信任https://vcsjones.com/2015/05/04/authenticating-asp-net-5-to-ad-fs-oauth/

您需要将信赖方信任的id添加到属性文件userAuthorizationUri中作为参数'resource'的值。

声明规则:

如果你不希望有创建自己的PrincipalExtractor或AuthoritiesExtractor(见AdfsUserInfoTokenServices代码),设置属性无论您正在使用的用户名(如SAM-帐户 - 名称),以便它具有传出声明类型“用户名”。在为组创建声明规则时,请确保声明类型是“权限”(ADFS只是让我键入该声明,不存在该名称的现有声明类型)。否则,您可以编写提取器来处理ADFS索赔类型。

一旦完成了这一切,你应该有一个工作的例子。这里有很多细节,但是一旦你把它弄清楚了,它不会太糟糕(比让SAML使用ADFS更容易)。关键是了解ADFS将数据嵌入到OAuth2令牌中的方式,并了解如何使用UserInfoTokenServices对象。希望这可以帮助别人。

+0

这可以用来集成OAuth2 + ADFS的Spring Rest API吗? –

+1

@Ashika,我不确定。我认为它目前仅限于使用表单登录,这对于单独使用rest api来说是不允许的。微软正在MS Server 2016中添加新功能,该功能可能提供以下功能:https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/development/enabling-oauth-confidential-clients-with -ad-FS-2016 –

0

@Erik,这是一个非常好的解释,说明如何使用ADFS作为身份和授权提供者。我偶然发现的事情是在JWT令牌中获得“upn”和“email”信息。这是解码JWT信息我收到 -

2017-07-13 19:43:15.548 INFO 3848 --- [nio-8080-exec-7] c.e.demo.AdfsUserInfoTokenServices  : Decoded JWT: {"aud":"http://localhost:8080/web-app","iss":"http://adfs1.example.com/adfs/services/trust","iat":1500000192,"exp":1500003792,"apptype":"Confidential","appid":"1fd9b444-8ba4-4d82-942e-91aaf79f5fd0","authmethod":"urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport","auth_time":"2017-07-14T02:43:12.570Z","ver":"1.0"} 

但加入后两个电子邮件-ID和UPN在根据“发行转换规则”,并加入“发送LDAP属性为索赔”权利规则以发送用户委托 - 以user_id命名(在FixedPrincipalExtractor - Spring安全性PRINCIPAL_KETS上)我能够记录用于在我的UI应用程序上登录的user_id。这里是解码的智威汤逊职位添加声明规则 -

2017-07-13 20:16:05.918 INFO 8048 --- [nio-8080-exec-3] c.e.demo.AdfsUserInfoTokenServices  : Decoded JWT: {"aud":"http://localhost:8080/web-app","iss":"http://adfs1.example.com/adfs/services/trust","iat":1500002164,"exp":1500005764,"upn":"[email protected]","apptype":"Confidential","appid":"1fd9b444-8ba4-4d82-942e-91aaf79f5fd0","authmethod":"urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport","auth_time":"2017-07-14T03:16:04.745Z","ver":"1.0"}