Closed quinnjr closed 2 weeks ago
Same issue, Confirming downgrading to 3.314.2 corrected the issue.
Hi all,
Sorry to hear about the issues. Looking into this now.
This was caused by a discrepancy in the noAuth
value in our specification vs what was actually modeled. We recently released a feature which allows services to model multiple auth types for the service as a whole, as well as certain operations— the getUser
operation uses the auth type that the discrepancy lies with. This should be fixed in today's release.
This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.
Describe the bug
As of roughly 2:00PM on 6/17/2024, we've been unable to establish client connections to Cognito to verify access tokens that are produced by the service.
Error output:
Could not resolve an authentication scheme: The service does not support
smithy.api#noAuthauthentication.
Expected Behavior
Connect to Cognito and verify access token
Current Behavior
No connection to Cognito can be established
Reproduction Steps
Example code:
$config['aws']['credentials']
is a correct associative array with valid access credentials.Possible Solution
No response
Additional Information/Context
No response
SDK version used
3.314.3
Environment details (Version of PHP (
php -v
)? OS name and version, etc.)PHP 8.2.15, Ubuntu 22.04