soto-cognito-authentication-kit

Major release changes

• Uses soto v7
• Uses jwt-kit v5
• Requires swift 6

Breaking changes

• Using jwt-kit v5

Minor release changes

• Require Swift 6 as jwt-kit v5 requires it

• Use Soto 7.0.0
• Use JWTKit 5.0.0-rc.1

• Use jwt-kit v5 beta to avoid symbol clash with swift-crypto

• Loosen swift-crypto version requirements

• Loosen swift-crypto version requirements

Update to use 7.0 beta of Soto

Update to use 7.0 alpha of Soto

Patch release changes

• Use en_US_POSIX in dateFormatter used by SRP code

Minor release changes

• Update minimum required Swift version to 5.6.
  • Remove all #if compiler checks for Swift concurrency and Sendable conformance
  • Replace _SotoSendable with Sendable

Major release changes

• Using Soto v6
• Add Logger parameter to many public symbols
• ChallengedResponse.name is a CognitoChallengeName? instead of String?.
• Added Sendable conformance to relevant symbols
• Protect access to CognitoAuthenticatable.jwtSigners with a lock

Other changes

• Add API breakage GitHub action to be run on all PRs
• sanity script has been renamed to validity

• Fixed missing @available tag

Revert concurrency availability checks to macOS 12, iOS 15 etc

• Swift concurrency APIs are now available for macOS 10.15, iOS 13, tvOS 13 and watchOS 6

Minor release changes

• Added Cognito Userpool credential provider. PR #22
• Added Support for async/await. PR #24

• Add tvOS as a supported platform

• Remove requireAuthenticatedClient function parameter from functions and replace with adminClient member variable of CognitoConfiguration.
• Add more helpful error messages when trying to call functions that required an authenticated AWSClient.

• Add forgotPassword and confirmForgotPassword
• Make eventLoop and contextData optional in CognitoAuthenticatable methods
• Remove CognitoAuthenticatable.respondTo.. function duplicates and give requireAuthenticatedClient a default value

• CognitoConfiguration.init parameter clientSecret has default value of nil.
• Fixed bug where username,password authentication wasn't setting the correct authorization flow when requireAuthenticatedClient was set to false.
• Deprecated respondToChallenge() with parameter requireAuthentication in favor of version with parameter requireAuthenticatedClient for consistency.
• Added versions of respondToNewPasswordChallenge and respondToMFAChallenge that include requireAuthenticatedClient parameter.
• Added test for unauthenticated client login

breaking change

• CognitoConfiguration.clientSecret is now optional