Releases: soto-project/soto-cognito-authentication-kit
Releases · soto-project/soto-cognito-authentication-kit
v4.0.0
Major release changes
- Using Soto v6
- Add
Logger
parameter to many public symbols ChallengedResponse.name
is aCognitoChallengeName?
instead ofString?
.- 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
v3.2.2
- Fixed missing @available tag
v3.2.1
Revert concurrency availability checks to macOS 12, iOS 15 etc
v3.2.0
- Swift concurrency APIs are now available for macOS 10.15, iOS 13, tvOS 13 and watchOS 6
v3.1.0
v3.0.1
- Add tvOS as a supported platform
v3.0.0
- Remove
requireAuthenticatedClient
function parameter from functions and replace withadminClient
member variable ofCognitoConfiguration
. - Add more helpful error messages when trying to call functions that required an authenticated
AWSClient
.
v2.3.0
- Add
forgotPassword
andconfirmForgotPassword
- Make
eventLoop
andcontextData
optional inCognitoAuthenticatable
methods - Remove
CognitoAuthenticatable.respondTo..
function duplicates and giverequireAuthenticatedClient
a default value
v2.2.0
CognitoConfiguration.init
parameterclientSecret
has default value ofnil
.- Fixed bug where username,password authentication wasn't setting the correct authorization flow when
requireAuthenticatedClient
was set to false. - Deprecated
respondToChallenge()
with parameterrequireAuthentication
in favor of version with parameterrequireAuthenticatedClient
for consistency. - Added versions of
respondToNewPasswordChallenge
andrespondToMFAChallenge
that includerequireAuthenticatedClient
parameter. - Added test for unauthenticated client login
v2.1.0
breaking change
- CognitoConfiguration.clientSecret is now optional