Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2.1.9 raising Aws::CognitoIdentity::Errors::MissingAuthenticationTokenException on every CognitoSync API Call #882

Closed
eniskonuk opened this issue Jul 29, 2015 · 5 comments
Labels
guidance Question that needs advice or information.

Comments

@eniskonuk
Copy link
Contributor

Upgrading to 2.1.9 has introduced this error on a valid list_identity_pools API call.

cogs = Aws::CognitoSync::Client.new(
:region => region, :credentials => @aws_cred, :logger => @aws_logger
)
respp = cogi.list_identity_pools( :max_results => MaxResults )
RAISE

Thx
Enis

@trevorrowe
Copy link
Member

Thank you for reporting this. I'm guessing that you meant that Aws::CognitoIdentity::Client#list_idenity_pools raises. The change that caused this regression comes from this pull-request:
#862

The following operations were white-listed to be sent as unsigned requests:

  • GetCredentialsForIdentity
  • GetId
  • GetOpenIdToken
  • ListIdentityPools
  • UnlinkDeveloperIdentity
  • UnlinkIdentity

I tested a few of these, but not all. Each of them do state quite clearly in their public API documentation the following:

This is a public API. You do not need any credentials to call this API.

I've gone back and tested all operations and found two of them that do require authentication despite the claims in the API reference:

http://docs.aws.amazon.com/cognitoidentity/latest/APIReference/API_ListIdentityPools.html
http://docs.aws.amazon.com/cognitoidentity/latest/APIReference/API_UnlinkDeveloperIdentity.html

I've corrected the code for these two operations and added integration tests to test these against live endpoints. Thank you for bringing this to our attention. I'll have a patch release out shortly.

@eniskonuk
Copy link
Contributor Author

Thanks @trevorrowe. Really appreciate the fast response.

@trevorrowe
Copy link
Member

I forgot to update, but 2.1.10 was released earlier today wight the patch.

@eniskonuk
Copy link
Contributor Author

Yes. I saw it and tested already. We will deploy as soon as we can.

Enis Konuk
[email protected]
978-760-0732

On Jul 29, 2015, at 8:42 PM, Trevor Rowe [email protected] wrote:

I forgot to update, but 2.1.10 was released earlier today wight the patch.


Reply to this email directly or view it on GitHub.

@trevorrowe
Copy link
Member

Also worth noting, the API reference documentation has been corrected as well.

@srchase srchase added guidance Question that needs advice or information. bug labels Dec 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
guidance Question that needs advice or information.
Projects
None yet
Development

No branches or pull requests

3 participants