You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
According to AWS STS GetCallerIdentity Docs, the request to the service should be a POST https://sts.amazonaws.com with data Action=GetCallerIdentity&Version=2011-06-15 instead of a GET https://sts.amazonaws.com/?Action=GetCallerIdentity&Version=2011-06-15.
A clear and concise description of what the problem is. Ex. I would like to see [...] because [...].
I would like to see a post request (in addition to the get request to keep backwards compatibility) because a post request is the documented and preferred API of sts.
Describe the solution you would like
A fallback of POST request to GET request to AWS STS service.
The text was updated successfully, but these errors were encountered:
@izgeri It's an enhancement since the current one still works (even though it uses unknown API of STS) but we cannot rely that this API will stay available for us. Waiting for @InbalZilberman to confirm the fallback and I will push the changes
Is your feature request related to a problem? Please describe.
According to AWS STS GetCallerIdentity Docs, the request to the service should be a
POST https://sts.amazonaws.com
with dataAction=GetCallerIdentity&Version=2011-06-15
instead of aGET https://sts.amazonaws.com/?Action=GetCallerIdentity&Version=2011-06-15
.A clear and concise description of what the problem is. Ex.
I would like to see [...] because [...]
.I would like to see a post request (in addition to the get request to keep backwards compatibility) because a post request is the documented and preferred API of sts.
Describe the solution you would like
A fallback of
POST
request toGET
request to AWS STS service.The text was updated successfully, but these errors were encountered: