尝试在资源服务器上运行集成测试时无效的令牌错误

发布于 2025-02-13 15:46:57 字数 2376 浏览 0 评论 0原文

我一直在玩这个示例这是一个简单的资源服务器,我重点关注集成测试由于我想在自己的项目上实现相同的测试,但是我试图用Spring授权服务器生成的集成测试中使用的令牌示例

但是,当试图用spring授权服务器样本中的令牌替换资源服务器示例的访问令牌时,它会抛出www-authentate “,error_description =”试图解码JWT时发生错误:签名的JWT被拒绝:预期的另一种算法,或没有匹配键(s)找到“,errir_uri =” https://tools.ietf.org/html/rfc6750#section-3.1“”

我在资源服务器样本中替换了ocy> mock> mocke> mockweberverproperperpertysource JWKS“ n”参数带有授权服务器示例自己的“ n”参数,但毫无用处,它仍然返回相同的错误。

尽管从Auth Server示例中返回的访问令牌和样本上的Orignal Resource Server令牌有些不同,尽管我不知道为什么它在集成测试中不起作用。

我在做什么错,如何从文件oauth2reserverserapplicationestests中的集成测试中替换令牌,以添加我自己并正常工作?

来自示例的春季授权服务器令牌:

eyJraWQiOiIwMjg2OWFlZC1hZjQwLTQ5MmEtYWFlYy1mMWZhMTI1N2UzZWUiLCJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJtZXNzYWdpbmctY2xpZW50IiwiYXVkIjoibWVzc2FnaW5nLWNsaWVudCIsIm5iZiI6MTY1NzExNDQ3OCwic2NvcGUiOlsibWVzc2FnZTpyZWFkIl0sImlzcyI6Imh0dHA6XC9cL2xvY2FsaG9zdDo5MDAwIiwiZXhwIjoxNjU3MTE0Nzc4LCJpYXQiOjE2NTcxMTQ0Nzh9.IB57Lix9R6F7sL5Ai5hc0o8DbWfxzXCnCEp6HL8vYu3XyVYx-wPthb5vTX4vsoBrebFsgIBkO63At4R3mfpkJSZO72bA7o-OkJEW0-n3MQwTRDZssy7-wvCG_dnRJ2OPlInaXqOogzWRfETI-7l_Ey5pxjQoKUGzA0Omqm2OtdVzy5X7qUlsDJ3rYuI34092bTZJGP3O3RuXkuJaP6GSkhG4sForttj6aFMviXDPeNJ5zpuyWBMC5bRunvVhCo2NOkHoL8BMr1s8FLySrNCGbIEOE9lkZxDJ3LZ7pH3hsbFuhn7jXYlZ4J5sFEu6c0kHHVLU7ti4cm_7VYp7DRV91g

原始资源服务器样本令牌:

eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJzdWJqZWN0IiwiZXhwIjoyMTY0MjQ1NjQ4LCJhdXRob3JpdGllcyI6WyJST0xFX1VTRVIiXSwianRpIjoiY2I1ZGMwNDYtMDkyMi00ZGJmLWE5MzAtOGI2M2FhZTYzZjk2IiwiY2xpZW50X2lkIjoicmVhZGVyIiwic2NvcGUiOlsibWVzc2FnZTpyZWFkIl19.Pre2ksnMiOGYWQtuIgHB0i3uTnNzD0SMFM34iyQJHK5RLlSjge08s9qHdx6uv5cZ4gZm_cB1D6f4-fLx76bCblK6mVcabbR74w_eCdSBXNXuqG-HNrOYYmmx5iJtdwx5fXPmF8TyVzsq_LvRm_LN4lWNYquT4y36Tox6ZD3feYxXvHQ3XyZn9mVKnlzv-GCwkBohCR3yPow5uVmr04qh_al52VIwKMrvJBr44igr4fTZmzwRAZmQw5rZeyep0b4nsCjadNcndHtMtYKNVuG5zbDLsB7GGvilcI9TDDnUXtwthB_3iq32DAd9x8wJmJ5K8gmX6GjZFtYzKk_zEboXoQ

I've been playing with this sample that it's a simple resource server, I'm focusing on the integration tests since I want to implement the same on my own projects, but I'm trying to replace the tokens used on the integration tests with the ones that are generated from the Spring Authorization Server sample

But when trying to replace the access tokens from the resource server sample with the tokens from the Spring Authorization Server sample it throws an WWW-Authenticate:"Bearer error="invalid_token", error_description="An error occurred while attempting to decode the Jwt: Signed JWT rejected: Another algorithm expected, or no matching key(s) found", error_uri="https://tools.ietf.org/html/rfc6750#section-3.1""

I have replaced in the resource server sample the MockWebServerPropertySource JWKS "n" parameter with the Authorization Server sample own "n" parameter from the JWKS, but to no avail it still returns the same error.

Though the access token returned from the auth server sample and the orignal resource server token on the sample are a little bit different, though I don't know why it wouldn't work on the integration tests.

What I'm doing wrong and how do I replace the tokens from the integration test in the file OAuth2ResourceServerApplicationITests to add my own and work properly?

Spring Authorization Server token from sample:

eyJraWQiOiIwMjg2OWFlZC1hZjQwLTQ5MmEtYWFlYy1mMWZhMTI1N2UzZWUiLCJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJtZXNzYWdpbmctY2xpZW50IiwiYXVkIjoibWVzc2FnaW5nLWNsaWVudCIsIm5iZiI6MTY1NzExNDQ3OCwic2NvcGUiOlsibWVzc2FnZTpyZWFkIl0sImlzcyI6Imh0dHA6XC9cL2xvY2FsaG9zdDo5MDAwIiwiZXhwIjoxNjU3MTE0Nzc4LCJpYXQiOjE2NTcxMTQ0Nzh9.IB57Lix9R6F7sL5Ai5hc0o8DbWfxzXCnCEp6HL8vYu3XyVYx-wPthb5vTX4vsoBrebFsgIBkO63At4R3mfpkJSZO72bA7o-OkJEW0-n3MQwTRDZssy7-wvCG_dnRJ2OPlInaXqOogzWRfETI-7l_Ey5pxjQoKUGzA0Omqm2OtdVzy5X7qUlsDJ3rYuI34092bTZJGP3O3RuXkuJaP6GSkhG4sForttj6aFMviXDPeNJ5zpuyWBMC5bRunvVhCo2NOkHoL8BMr1s8FLySrNCGbIEOE9lkZxDJ3LZ7pH3hsbFuhn7jXYlZ4J5sFEu6c0kHHVLU7ti4cm_7VYp7DRV91g

Original resource server sample token:

eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJzdWJqZWN0IiwiZXhwIjoyMTY0MjQ1NjQ4LCJhdXRob3JpdGllcyI6WyJST0xFX1VTRVIiXSwianRpIjoiY2I1ZGMwNDYtMDkyMi00ZGJmLWE5MzAtOGI2M2FhZTYzZjk2IiwiY2xpZW50X2lkIjoicmVhZGVyIiwic2NvcGUiOlsibWVzc2FnZTpyZWFkIl19.Pre2ksnMiOGYWQtuIgHB0i3uTnNzD0SMFM34iyQJHK5RLlSjge08s9qHdx6uv5cZ4gZm_cB1D6f4-fLx76bCblK6mVcabbR74w_eCdSBXNXuqG-HNrOYYmmx5iJtdwx5fXPmF8TyVzsq_LvRm_LN4lWNYquT4y36Tox6ZD3feYxXvHQ3XyZn9mVKnlzv-GCwkBohCR3yPow5uVmr04qh_al52VIwKMrvJBr44igr4fTZmzwRAZmQw5rZeyep0b4nsCjadNcndHtMtYKNVuG5zbDLsB7GGvilcI9TDDnUXtwthB_3iq32DAd9x8wJmJ5K8gmX6GjZFtYzKk_zEboXoQ

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文