invalid_request: Unexpected client assertion type, when using certificates based authorization
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- php
- 领域
- api, authentication
调研方向
从 AuthorizationCodeCertificateContext、InMemoryAccessTokenCache 和 GraphPhpLeagueAccessTokenProvider 入手,然后跟踪报告中所示的 refresh token 请求。将基于证书的 refresh 行为与正常工作的基于 secret 的流程进行比较;当存储的 refresh token 能够在不出现 AADSTS90023 的情况下刷新 access token 时,该问题即告解决。
由索引模型根据 Issue 内容生成。
描述
Describe the bug
Hello, I'm trying to use certificates (self-signed) based authorization for getting access tokens on behalf of user (their outlook calendar resources).
I'm using AuthorizationCodeCertificateContext to acquire initial access and refresh tokens, then I store them in db for later usage.
Using stored access token works well until it expires, when I get invalid_request error when sdk tries to refresh access token, again using stored refresh token
I'm not sure how am I able to get access and refresh tokens using AuthorizationCodeCertificateContext, then use access token successfully to fetch some user resources, but not able to refresh access token.
Expected behavior
If I understand token management correctly, expected behavior should be that refreshing token just works out of the box if I provide refresh token to InMemoryAccessTokenCache.
I tried same thing using secrets instead of certificates, it works as expected.
Also checked if sdk actually is trying to refresh token and is sending proper request, it should be okay as well:
method: POST
url: https://login.microsoftonline.com/{my-tenant-id}/oauth2/v2.0/token
headers: [
"content-type" => "application/x-www-form-urlencoded"
]
body:
"client_id" => "abc"
"grant_type" => "refresh_token"
"client_assertion" => "eyJ0eXAiOiJKV1QiLCJ4NXQiOiJXUklac2RPRE9WaHlxTWFoQ2VfYUxnTHdGTE0iLCJhbGciOiJSUzI1NiJ9.eyJhdWQiOiJodHRwczovL2xvZ2luLm1pY3Jvc29mdG9ubGluZS5jb20vZTU0OGZkOWQtZmJmZC0..."
"client_assertion_type" => "urn:ietf:params:Oauth:client-assertion-type:jwt-bearer"
"refresh_token" => "1.AR8Anf1I5f372U6UbFh_vPA_wn8-2g2i6gpHmbfGx5rrSzccAfUfAA.AgABAwEAAABVrSpeuWamRam2jAF1XRQEAwDs_..."
How to reproduce
this is how I created self-signed CA:
$privateKeyOptions = [
'digest_alg' => OPENSSL_ALGO_SHA256,
'private_key_bits' => 2048,
'private_key_type' => OPENSSL_KEYTYPE_RSA,
];
// Generate a new private key
$privateKey = openssl_pkey_new($privateKeyOptions);
if ($privateKey === false) {
throw new RuntimeException(sprintf('Failed to generate private key: %s', openssl_error_string()));
}
// Generate a certificate signing request
$csr = openssl_csr_new([
'countryName' => 'xx',
'stateOrProvinceName' => 'xxxx',
'localityName' => 'xx',
'organizationName' => 'xx',
'commonName' => 'localhost',
], $privateKey, $privateKeyOptions);
if (is_bool($csr)) {
throw new RuntimeException(sprintf('Failed to open RSA key: %s', openssl_error_string()));
}
// Generate a self-signed certificate valid for 1 year
$certificate = openssl_csr_sign(
csr: $csr,
ca_certificate: null,
private_key: $privateKey,
days: CertificateRotatorInterface::MAX_DURATION_IN_DAYS
);
if ($certificate === false) {
throw new RuntimeException(sprintf('Failed to sign data: %s', openssl_error_string()));
}
// Export the certificate and key to files
$certificateFilePath = '/tmp/tls_crt.pem';
$privateKeyFilePath = '/tmp/tls_key.pem';
if (!openssl_x509_export_to_file($certificate, $certificateFilePath)) {
throw new RuntimeException(sprintf('Failed to export certificate: %s', openssl_error_string()));
}
if (!openssl_pkey_export_to_file($privateKey, $privateKeyFilePath)) {
throw new RuntimeException(sprintf('Failed to export private key: %s', openssl_error_string()));
}
tls_crt.pem file is uploaded through Microsoft Entra Admin to an application I registered for testing.
GraphServiceClient setup:
(I use "code_verifier" while getting authorization code, here it's just some placeholder value)
$tokenRequestContext = new AuthorizationCodeCertificateContext(
tenantId: $tenantId,
clientId: $clientId,
authCode: 'default',
redirectUri: $redirectUri,
certificatePath: $certificatePath,
privateKeyPath: $privateKeyPath,
additionalParams: ['code_verifier' => 'default']
);
$inMemoryCache = new InMemoryAccessTokenCache(
$tokenRequestContext,
new AccessToken([
'access_token' => $token['accessToken'],
'refresh_token' => $token['refreshToken'],
'expires' => $token['expires'],
])
);
$graphServiceClient = GraphServiceClient::createWithAuthenticationProvider(
GraphPhpLeagueAuthenticationProvider::createWithAccessTokenProvider(
GraphPhpLeagueAccessTokenProvider::createWithCache(
$accessTokenCache,
$tokenRequestContext,
$scopes
)
)
);
dump($graphServiceClient->me()->get()->wait());
SDK Version
2.30.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
League\OAuth2\Client\Provider\Exception\IdentityProviderException {
#response: array:6 [
"error" => "invalid_request"
"error_description" => "AADSTS90023: Unexpected client assertion type. Trace ID: a0dfae09-fd6a... Correlation ID: ae87cdb5-9cb1-4a43... Timestamp: 2025-03-24 14:15:17Z "
"error_codes" => array:1 [
0 => 90023
]
"timestamp" => "2025-03-24 14:15:17Z"
"trace_id" => "a0dfae09-fd6a-482f..."
"correlation_id" => "ae87cdb5-9cb1-4a43..."
]
}
Configuration
docker base image: php:8.4-fpm-alpine3.21
Other information
No response
- 主要语言
- PHP
- 星标
- 669
- 派生
- 149
- 平均合并
- 1 天 4 小时
- 30 天内合并 PR
- 5
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoftgraph/msgraph-sdk-php 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
microsoftgraph/msgraph-sdk-php#1794 · 2 条评论 ·
-
bug: metadata type:bug
难度 1/5 1 小时以内 新手友好度 88/100
microsoftgraph/msgraph-sdk-php#1739 · 6 条评论 ·
-
status:waiting-for-triage type:bug
难度 1/5 1 小时以内 新手友好度 68/100
microsoftgraph/msgraph-sdk-php#1643 · 8 条评论 · 4 个 reaction ·
-
status:waiting-for-triage
难度 5/5 一周以上 新手友好度 35/100
microsoftgraph/msgraph-sdk-php#1800 · 3 个 reaction ·
-
Now未关闭
难度 5/5 一周以上 新手友好度 1/100
microsoftgraph/msgraph-sdk-php#1799 ·
查看 microsoftgraph/msgraph-sdk-php 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
matomo-org/plugin-CustomAlerts#310 ·
维护者通常 1 天内回复
-
Bug Status: Needs Triage
难度 1/5 1 小时以内 新手友好度 68/100
维护者通常 1 天内回复
-
domain/checkout Platform(Default) priority/low testing/acceptance
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
pluginsGLPI/addressing#132 ·
-
5.14.0 PIE packages still declare PHP >=8.3, so PIE installs them on PHP 8.3 and the build fails未关闭
难度 2/5 1-3 小时 新手友好度 66/100