diff --git a/Cartfile b/Cartfile index f5a715d..9920c42 100644 --- a/Cartfile +++ b/Cartfile @@ -1 +1 @@ -github "wultra/networking-apple" "1.4.0" +github "wultra/networking-apple" "release/1.5.x" \ No newline at end of file diff --git a/Cartfile.resolved b/Cartfile.resolved index 28d9b28..4ca62f1 100644 --- a/Cartfile.resolved +++ b/Cartfile.resolved @@ -1,3 +1,3 @@ -binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.8.0/PowerAuth2.json" "1.8.0" -binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.8.0/PowerAuthCore.json" "1.8.0" -github "wultra/networking-apple" "1.4.0" +binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.9.0/PowerAuth2.json" "1.9.0" +binary "https://raw.githubusercontent.com/wultra/powerauth-mobile-sdk-spm/1.9.0/PowerAuthCore.json" "1.9.0" +github "wultra/networking-apple" "b1f9c2f328c4857407499786c334ccd0f764d7d9" diff --git a/Deploy/WultraMobileTokenSDK.podspec b/Deploy/WultraMobileTokenSDK.podspec index 34c1d92..e5c076d 100644 --- a/Deploy/WultraMobileTokenSDK.podspec +++ b/Deploy/WultraMobileTokenSDK.podspec @@ -18,8 +18,8 @@ Pod::Spec.new do |s| # 'Common' subspec s.subspec 'Common' do |sub| sub.source_files = 'WultraMobileTokenSDK/Common/**/*.swift' - sub.dependency 'PowerAuth2', '~> 1.8.0' - sub.dependency 'WultraPowerAuthNetworking', '~> 1.4.0' + sub.dependency 'PowerAuth2', '~> 1.9.0' + sub.dependency 'WultraPowerAuthNetworking', '~> 1.5.0' end # 'Operations' subspec diff --git a/Package.swift b/Package.swift index 5acdc44..fa4e81c 100644 --- a/Package.swift +++ b/Package.swift @@ -11,8 +11,8 @@ let package = Package( .library(name: "WultraMobileTokenSDK", targets: ["WultraMobileTokenSDK"]) ], dependencies: [ - .package(url: "https://github.com/wultra/powerauth-mobile-sdk-spm.git", .upToNextMinor(from: "1.8.0")), - .package(url: "https://github.com/wultra/networking-apple.git", .upToNextMinor(from: "1.4.0")) + .package(url: "https://github.com/wultra/powerauth-mobile-sdk-spm.git", .upToNextMinor(from: "1.9.0")), + .package(url: "https://github.com/wultra/networking-apple.git", .upToNextMinor(from: "1.5.0")) ], targets: [ .target( diff --git a/README.md b/README.md index c17f8b4..71a2085 100644 --- a/README.md +++ b/README.md @@ -20,13 +20,13 @@ __Wultra Mobile Token SDK__ is a high-level SDK for operation approval. -With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https://github.com/wultra/powerauth-mobile-sdk). It communicates with the "Mobile Token REST API" and "Mobile Push Registration API". Individual endpoints are described in the [PowerAuth Webflow documentation](https://github.com/wultra/powerauth-webflow/). +With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https://github.com/wultra/powerauth-mobile-sdk). It communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API). To understand the Wultra Mobile Token SDK purpose on a business level better, you can visit our own [Mobile Token application](https://www.wultra.com/mobile-token). We use Wultra Mobile Token SDK in our mobile token application as well. WMT SDK library does precisely this: -- Retrieves the list of operations that are pending for approval for a given user. +- Retrieves the list of operations that are pending approval for a given user. - Approves or rejects operations with PowerAuth transaction signing. - Registers an existing PowerAuth activation to receive push notifications. diff --git a/WultraMobileTokenSDK.podspec b/WultraMobileTokenSDK.podspec index 8a8d534..759d713 100644 --- a/WultraMobileTokenSDK.podspec +++ b/WultraMobileTokenSDK.podspec @@ -18,8 +18,8 @@ Pod::Spec.new do |s| # 'Common' subspec s.subspec 'Common' do |sub| sub.source_files = 'WultraMobileTokenSDK/Common/**/*.swift' - sub.dependency 'PowerAuth2', '~> 1.8.0' - sub.dependency 'WultraPowerAuthNetworking', '~> 1.4.0' + sub.dependency 'PowerAuth2', '~> 1.9.0' + sub.dependency 'WultraPowerAuthNetworking', '~> 1.5.0' end # 'Operations' subspec diff --git a/docs/Changelog.md b/docs/Changelog.md index 3ffb736..a0373cd 100644 --- a/docs/Changelog.md +++ b/docs/Changelog.md @@ -1,5 +1,11 @@ # Changelog +## 1.12.0 (October 2024) + +- PowerAuth "server stack" `1.9+` is now required +- Dependency `powerauth-mobile-sdk` is now required in version `1.9.x` +- Dependency `networking-apple` is now required in version `1.5.x` + ## 1.11.1 (July 2024) - Dependency `networking-apple` is now required in version `1.4.x` diff --git a/docs/Readme.md b/docs/Readme.md index 90a99ec..4147bc6 100644 --- a/docs/Readme.md +++ b/docs/Readme.md @@ -1,12 +1,12 @@ # Wultra Mobile Token SDK for iOS -With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https://github.com/wultra/powerauth-mobile-sdk). It communicates with the "Mobile Token REST API" and "Mobile Push Registration API". Individual endpoints are described in the [PowerAuth Webflow documentation](https://github.com/wultra/powerauth-webflow/). +With Wultra Mobile Token (WMT) SDK, you can integrate an out-of-band operation approval into an existing mobile app, instead of using a standalone mobile token application. WMT is built on top of [PowerAuth Mobile SDK](https://github.com/wultra/powerauth-mobile-sdk). It communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API). To understand the Wultra Mobile Token SDK purpose on a business level better, you can visit our own [Mobile Token application](https://www.wultra.com/mobile-token). We use Wultra Mobile Token SDK in our mobile token application as well. WMT SDK library does precisely this: -- Retrieves the list of operations that are pending for approval for a given user. +- Retrieves the list of operations that are pending approval for a given user. - Approves or rejects operations with PowerAuth transaction signing. - Registers an existing PowerAuth activation to receive push notifications. diff --git a/docs/Using-Inbox-Service.md b/docs/Using-Inbox-Service.md index 59ed925..e7a8e53 100644 --- a/docs/Using-Inbox-Service.md +++ b/docs/Using-Inbox-Service.md @@ -19,6 +19,8 @@ Inbox Service is responsible for managing messages in the Inbox. The inbox is a Note: Before using Inbox Service, you need to have a `PowerAuthSDK` object available and initialized with a valid activation. Without a valid PowerAuth activation, the service will return an error. +Inbox Service communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API). + ## Creating an Instance ### On Top of the `PowerAuthSDK` instance diff --git a/docs/Using-Operations-Service.md b/docs/Using-Operations-Service.md index b49a076..d26a695 100644 --- a/docs/Using-Operations-Service.md +++ b/docs/Using-Operations-Service.md @@ -29,7 +29,7 @@ An operation can be anything you need to be approved or rejected by the user. It Note: Before using Operations Service, you need to have a `PowerAuthSDK` object available and initialized with a valid activation. Without a valid PowerAuth activation, all endpoints will return an error -Operations Service communicates with a backend via [Mobile Token API endpoints](https://github.com/wultra/powerauth-webflow/blob/develop/docs/Mobile-Token-API.md). +Operations Service communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API). ## Creating an Instance @@ -745,10 +745,10 @@ public struct WMTPACData: Decodable { - two methods are provided: - `parseDeeplink(url: URL) -> WMTPACData?` - URI is expected to be in the format `scheme://code=$JWT` or `scheme://operation?oid=5b753d0d-d59a-49b7-bec4-eae258566dbb&potp=12345678` - `parseQRCode(code: String) -> WMTPACData?` - code is to be expected in the same format as deeplink formats or as a plain JWT - - mentioned JWT should be in the format `{“typ”:”JWT”, “alg”:”none”}.{“oid”:”5b753d0d-d59a-49b7-bec4-eae258566dbb”, “potp”:”12345678”} ` + - mentioned JWT should be in the format `{"type":"JWT", "alg":"none"}.{"oid":"5b753d0d-d59a-49b7-bec4-eae258566dbb", "potp":"12345678"} ` - Accepted formats: - - notice that totp key in JWT and in query shall be `potp`! + - notice that the totp key in JWT and query shall be `potp`! ## Error handling diff --git a/docs/Using-Push-Service.md b/docs/Using-Push-Service.md index e98677d..80894d4 100644 --- a/docs/Using-Push-Service.md +++ b/docs/Using-Push-Service.md @@ -17,7 +17,7 @@ Push Service is responsible for registering the device for the push notification Note: Before using Push Service, you need to have a `PowerAuthSDK` object available and initialized with a valid activation. Without a valid PowerAuth activation, the service will return an error -Push Service communicates with [Mobile Push Registration API](https://github.com/wultra/powerauth-webflow/blob/develop/docs/Mobile-Push-Registration-API.md). +Push Service communicates with the [Mobile Token API](https://developers.wultra.com/components/enrollment-server/develop/documentation/Mobile-Token-API). ## Creating an Instance diff --git a/scripts/cart-update.sh b/scripts/cart-update.sh index 0b071f2..d5254a9 100755 --- a/scripts/cart-update.sh +++ b/scripts/cart-update.sh @@ -5,5 +5,5 @@ set -e # stop sript when error occures SCRIPT_FOLDER=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd ) pushd "${SCRIPT_FOLDER}/.." -carthage bootstrap --use-xcframeworks --use-submodules --platform ios --configuration Debug +carthage update --use-xcframeworks --use-submodules --platform ios --configuration Debug popd \ No newline at end of file