Added support for Bot Protection verification [SDK-1867] #629
Conversation
| @@ -1431,7 +1431,6 @@ | |||
| OTHER_SWIFT_FLAGS = ""; | |||
| PRODUCT_BUNDLE_IDENTIFIER = com.auth0.Lock; | |||
| PRODUCT_NAME = "$(TARGET_NAME)"; | |||
| PROVISIONING_PROFILE = "97f7985c-a5ce-42be-a3e5-39a6c818bc78"; | |||
There was a problem hiding this comment.
This provisioning profile was always hardcoded into the test app and was a nuisance since you had to remove it manually to run the app in a physical device. The app should have no references to any certificates or provisioning profiles.
| default: | ||
| return true | ||
| } | ||
| } | ||
| } | ||
|
|
||
| extension CredentialAuthError: Equatable { |
There was a problem hiding this comment.
The error must implement Equatable for the test matcher to correctly compare the expected vs the actual.
There was a problem hiding this comment.
Because this enum has associated values; in regular enums (meaning, enums without associated values) it's not necessary to add Equatable conformance.
| @@ -103,7 +105,19 @@ struct DatabaseInteractor: DatabaseAuthenticatable, DatabaseUserCreator, Loggabl | |||
|
|
|||
| self.credentialAuth | |||
| .request(withIdentifier: identifier, password: password, options: self.options) | |||
| .start { self.handle(identifier: identifier, result: $0, callback: callback) } | |||
| .start { result in | |||
There was a problem hiding this comment.
I'm basically chaining two interactors together, and wrapping the error of the second in an error of the first.
Changes
This PR adds support for the Bot Protection feature that requires a web-based verification step when the database login/signup request is flagged as suspicious. The verification step is implemented with Universal Login, and will automatically kick in when the
.isAuthenticationRequirederror is returned by Auth0.swift.Testing
Both login and signup flows were also tested manually.
Checklist