blocks|key|61486|text|如文件所述：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61487|Content必须始终是“application/x+form-urlencoded”。|blockquote|61488|来源：https://docs.aws.amazon.com/cognito/latest/developerguide/token-endpoint.html|offset|length|61489|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.aws.amazon.com/cognito/latest/developerguide/token-endpoint.html^0|0|0|3|25|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|S|8|@]|9|@$G|T|H|U|1|V]]|A|$]]|$1|I|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

As stated in the documentation:

<blockquote>
 Content-Type
 Must always be 'application/x-www-form-urlencoded'.
</blockquote>

Source: <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/token-endpoint.html" rel="noreferrer">https://docs.aws.amazon.com/cognito/latest/developerguide/token-endpoint.html</a>

blocks|key|1511769|text|使用身份验证的BasicAuth并提供Username=client_id，Password=client_secret|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1511770|使用POST方法|1511771|使用Body+=+x-www-form-urlencoded|1511772|不要忘记在身体中使用State值。|1511773|entityMap^0|J|8|S|9|12|8|1B|D|0|2|4|0|2|4|9|L|0|A|5|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|M|$]]

Use BasicAuth of Authentication and provide <code>Username</code>=<code>client_id</code>, <code>Password</code>=<code>client_secret</code>

Use <code>POST</code> method

Use <code>Body</code> = <code>x-www-form-urlencoded</code>

Dont forget to use <code>State</code> value in Body as well.

blocks|key|61456|text|我也有过类似的问题。在我的例子中，我不得不将Accept头更改为*/*。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|61457|当我将它作为Accept=text/html,application/xhtml%2Bxml,application/xml时，它对/token端点的响应为405。希望这能帮到别人。|61458|entityMap^0|W|3|0|6|1I|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

I had a similar problem. In my case I had to change the Accept header to <code>*/*</code>.

When I had it as <code>Accept=text/html,application/xhtml+xml,application/xml</code> it responded with 405 to the /token endpoint. Hopefully that helps somebody.

blocks|key|61566|text|我用c#编写了带有authorization_code授予类型的令牌代码，所有调用都失败了，而405方法不允许状态。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61567|根据AWS文档，应该使用以下URL和参数|61568|POST+https://mydomain.auth.us-east-1.amazoncognito.com/oauth2/token&
Content-Type='application/x-www-form-urlencoded'&
Authorization=Basic+aSdxd892iujendek328uedj

grant_type=authorization_code&
client_id=djc98u3jiedmi283eu928&
code=AUTHORIZATION_CODE&
redirect_uri=com.myclientapp://myclient/redirect|code-block|syntax|javascript|61569|花了2个小时后，我发现，从URL中删除&将解决这个问题，所以请确保您的请求如下所示|offset|length|style|BOLD|61570|POST+https://mydomain.auth.us-east-1.amazoncognito.com/oauth2/token
Content-Type='application/x-www-form-urlencoded'
Authorization=Basic+aSdxd892iujendek328uedj

grant_type=authorization_code&
client_id=djc98u3jiedmi283eu928&
code=AUTHORIZATION_CODE&
redirect_uri=com.myclientapp://myclient/redirect|61571|entityMap^0|0|0|0|J|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I was writing code in c# for token with authorization_code grant type and all calls were failing with 405 Method Not Allowed status.
According to AWS documentation following URL and parameters should be used
<pre><code>POST https://mydomain.auth.us-east-1.amazoncognito.com/oauth2/token&amp;
Content-Type='application/x-www-form-urlencoded'&amp;
Authorization=Basic aSdxd892iujendek328uedj

grant_type=authorization_code&amp;
client_id=djc98u3jiedmi283eu928&amp;
code=AUTHORIZATION_CODE&amp;
redirect_uri=com.myclientapp://myclient/redirect
</code></pre>
After spending 2 hours, I found out, removing &amp; from URL would solve the issue, so make sure your request looks like this
<pre><code>POST https://mydomain.auth.us-east-1.amazoncognito.com/oauth2/token
Content-Type='application/x-www-form-urlencoded'
Authorization=Basic aSdxd892iujendek328uedj

grant_type=authorization_code&amp;
client_id=djc98u3jiedmi283eu928&amp;
code=AUTHORIZATION_CODE&amp;
redirect_uri=com.myclientapp://myclient/redirect
</code></pre>

blocks|key|880954|text|以防万一对任何人都有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|880955|当我试图使用id_token作为authorization_code检索各自的jwt令牌(+access_token、grant_type、refresh_token)时，我面对的是405号邮递员。|blockquote|880956|原因是标题部分，其中我使用'application/x-www-form-urlencoded'作为Content-Type的值，即单引号。因此，当我删除这些单引号并且只使用application/x-www-form-urlencoded时，它就开始工作了。|offset|length|style|CODE|880957|entityMap^0|0|0|D|Z|1E|C|2F|X|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|O|8|@$G|P|H|Q|I|J]|$G|R|H|S|I|J]|$G|T|H|U|I|J]]|9|@]|A|$]]|$1|K|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|L|$]]

Well, just in case it helps anybody.
<blockquote>
I was facing a 405 in Postman while trying to retrieve the respective
jwt tokens (id_token, access_token, refresh_token) using the
grant_type as authorization_code.
</blockquote>
reason being the headers section where I was using <code>'application/x-www-form-urlencoded'</code> as value for <code>Content-Type</code> i.e. with single quotes. So, when I removed these single quotes and only used <code>application/x-www-form-urlencoded</code> right away, it started working.

blocks|key|1511859|text|通过如下所述的代码，我解决了AWS认知oauth2/token端点中不允许错误的错误405方法，它工作得很好。我从这个链接中获得帮助，并使用正确的格式在fetch请求中同时提到头参数和正文参数：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1511860|https://formcarry.com/documentation/fetch-api-example|1511861|++const+requestOptions+=+{
++++method:+"POST",
++++headers:+{
++++++"Content-Type":+"application/x-www-form-urlencoded",
++++++"Authorization":+`Basic+${authData}`,
++++++"Accept":+"application/json"++++++++++++
++++},
++++body:+`grant_type=${config.grant_type}&code=${code}&client_id=${config.clientId}&redirect_uri=${config.loginRedirectUri}`
++}
++++++++
++fetch(`${config.domainUrl}/oauth2/token`,+requestOptions)
++++.then(response+=>+response.json())
++++.then(data+=>+{
++++++sessionStorage.setItem("access_token",data.access_token)
++++++fetchUserDetails(data.access_token)
++++})|code-block|syntax|javascript|1511862|我使用一个配置文件来保存变量。|1511863|const+config+=+{
++domainUrl:+"https://domainname.auth.origin.amazoncognito.com",
++clientId:+"xxxxxxxxxxxx",
++loginRedirectUri:+"http://localhost:8000/redirecturi",
++grant_type:+"authorization_code",
++logoutUri:+"http://localhost:8000",
++clientSecret:+"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
}|1511864|entityMap|0|LINK|mutability|MUTABLE|url^0|J|C|0|0|1H|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|H|3|I|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|G]]]]

I resolved this error 405 method not allowed error in AWS Cognito <code>oauth2/token</code> endpoint by making my code as below mentioned, and it worked fine.
I took help from this link and use the correct format to mention both header and body parameters in the fetch request:
<a href="https://formcarry.com/documentation/fetch-api-example" rel="nofollow noreferrer">https://formcarry.com/documentation/fetch-api-example</a>
<pre class="lang-js prettyprint-override"><code> const requestOptions = {
 method: &quot;POST&quot;,
 headers: {
 &quot;Content-Type&quot;: &quot;application/x-www-form-urlencoded&quot;,
 &quot;Authorization&quot;: `Basic ${authData}`,
 &quot;Accept&quot;: &quot;application/json&quot; 
 },
 body: `grant_type=${config.grant_type}&amp;code=${code}&amp;client_id=${config.clientId}&amp;redirect_uri=${config.loginRedirectUri}`
 }
 
 fetch(`${config.domainUrl}/oauth2/token`, requestOptions)
 .then(response =&gt; response.json())
 .then(data =&gt; {
 sessionStorage.setItem(&quot;access_token&quot;,data.access_token)
 fetchUserDetails(data.access_token)
 })
</code></pre>
I used a config file to save variables.
<pre class="lang-js prettyprint-override"><code>const config = {
 domainUrl: &quot;https://domainname.auth.origin.amazoncognito.com&quot;,
 clientId: &quot;xxxxxxxxxxxx&quot;,
 loginRedirectUri: &quot;http://localhost:8000/redirecturi&quot;,
 grant_type: &quot;authorization_code&quot;,
 logoutUri: &quot;http://localhost:8000&quot;,
 clientSecret: &quot;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&quot;
}
</code></pre>

blocks|key|61733|text|我也有同样的问题，尽管我使用的是client_credentials而不是authorization_code。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61734|在Postman中，我使用了一个有效的client_id/client_secret作为用户名/密码的basic+auth，确保内容-Type：application/x-www-form-urlencoded标头在那里，并将body+(raw/json)设置为：|offset|length|style|CODE|61735|{
"client_id":+{client_id},
"grant_type":+"client_credentials",
"scope":+{client_scope}
}|code-block|syntax|javascript|61736|但是，我仍然得到了405:+Method+Not+Allowed错误。我最终发现我可以在邮递员中将身体类型转换为x-www-form-urlencoded，重新输入身体参数，现在它开始工作了。|61737|entityMap^0|0|J|9|T|D|20|X|3B|8|0|0|9|N|1K|L|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|P|$]]

I had the same issue, although using client_credentials rather than authorization_code.
In Postman I was using basic auth with a valid <code>client_id</code>/<code>client_secret</code> as username/password, made sure the Content-Type: <code>application/x-www-form-urlencoded</code> header was there, and set the body (<code>raw/json</code>) to:
<pre><code>{
&quot;client_id&quot;: {client_id},
&quot;grant_type&quot;: &quot;client_credentials&quot;,
&quot;scope&quot;: {client_scope}
}
</code></pre>
However, I was still getting the <code>405: Method Not Allowed</code> error.
I eventually figured out that I could switch the body type to <code>x-www-form-urlencoded</code> in Postman, re-entered the body parameters and now it's working.

blocks|key|61573|text|++++++++var+strClientSecret+=+$"{"your_clientId"}:{"your_clientsecret"}";
++++++++var+client+=+new+HttpClient();
++++++++var+body+=+new+Dictionary<string,+string>();
++++++++body.Add("grant_type",+"client_credentials");
++++++++body.Add("client_id",+"your_appclientid");
++++++++body.Add("redirect_uri",+"your_callbackurl");

++++++++var+content+=+new+FormUrlEncodedContent(body);
++++++++var+autho+=+System.Text.Encoding.UTF8.GetBytes(strClientSecret);
++++++++var+base64Autho+=+System.Convert.ToBase64String(autho);
++++++++client.DefaultRequestHeaders.Authorization+=+new+AuthenticationHeaderValue("Basic",+base64Autho);

++++++++client.DefaultRequestHeaders.TryAddWithoutValidation("Content-Type",+"application/x-www-form-urlencoded");

++++++++var+response+=+await+client.PostAsync("https://your_domain.auth.ap-south-1.amazoncognito.com/oauth2/token",+content);|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|61574|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code> var strClientSecret = $&quot;{&quot;your_clientId&quot;}:{&quot;your_clientsecret&quot;}&quot;;
 var client = new HttpClient();
 var body = new Dictionary&lt;string, string&gt;();
 body.Add(&quot;grant_type&quot;, &quot;client_credentials&quot;);
 body.Add(&quot;client_id&quot;, &quot;your_appclientid&quot;);
 body.Add(&quot;redirect_uri&quot;, &quot;your_callbackurl&quot;);

 var content = new FormUrlEncodedContent(body);
 var autho = System.Text.Encoding.UTF8.GetBytes(strClientSecret);
 var base64Autho = System.Convert.ToBase64String(autho);
 client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue(&quot;Basic&quot;, base64Autho);

 client.DefaultRequestHeaders.TryAddWithoutValidation(&quot;Content-Type&quot;, &quot;application/x-www-form-urlencoded&quot;);

 var response = await client.PostAsync(&quot;https://your_domain.auth.ap-south-1.amazoncognito.com/oauth2/token&quot;, content);
</code></pre>

blocks|key|61693|text|在我的例子中，在将axios从v0.x.x升级到v1.x.x之后，我更改了|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|61694|headers:+{+'content-type':+'application/x-www-form-urlencoded'+},|61695|至|61696|headers:+{+'Content-Type':+'application/x-www-form-urlencoded'+},|61697|在Content-Type中加上大写字母|61698|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/axios/axios^0|F|6|O|6|9|5|0|0|0|1T|0|0|0|1T|0|1|C|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]]|E|$]]|$1|F|3|G|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]]]

in my case after upgrade <a href="https://github.com/axios/axios" rel="nofollow noreferrer">axios</a> from <code>v0.x.x</code> to <code>v1.x.x</code> I changed
<code>headers: { 'content-type': 'application/x-www-form-urlencoded' },</code>
to
<code>headers: { 'Content-Type': 'application/x-www-form-urlencoded' },</code>
With capital letters in <code>Content-Type</code>

blocks|key|61780|text|为了使图片完整，如果您的主机标头没有设置或与您要发布的域不相同，您还将得到405+(不允许的方法)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61781|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

And to make the picture complete, if your Host header is not set or not the same as the domain that you are posting to, you will also get a 405 (Method not allowed).

I'm using AWS Cognito UI for login using authorization code grant flow and successfully getting the authorization code. But getting an 405 method not allowed error when post request is made to oauth2/token endpoint via postman

The app client is setup in Cognito User Pool with app secret passing appclientid:appclientsecret as authorization in base64 encoding.

405 method not allowed error in AWS Cognito oauth2/token endpoint

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我使用AWS认知UI登录，使用授权代码授权流，并成功地获得授权代码。但是在通过postman向OAuth2/令牌端点发出post请求时，获取405方法不允许出错app客户端设置在认知用户池中，应用程序秘密传递appclientid:appclientsecret作为base64编码中的授权。

问405方法不允许AWS认知OAuth2/令牌端点中的错误
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问405方法不允许AWS认知OAuth2/令牌端点中的错误EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问405方法不允许AWS认知OAuth2/令牌端点中的错误
EN