The SDK Configurator configures the Onegini SDK in your application project.

It currently supports iOS, Android, Cordova and NativeScript projects. For Cordova & NativeScript it supports both the iOS and Android platforms.

The tool was created to help developers to setup their apps to use the Onegini Mobile SDKs. The main responsibilities of the tool is to generate config models and perform certificate pinning. In order to perform both operations a ZIP file containing certificates and app config is needed. The file can be downloaded from the Token Server's Admin Panel.

You can download the latest compatible binary for your platform and SDK version from the Release page. Please have a look at the SDK compatibility in the next paragraph to choose the correct SDK configurator version.

The configurator binaries differ per SDK version. Please see the compatibility matrix below to choose the correct SDK configurator version:

Android SDK

iOS SDK

Cordova plugin

NativeScript plugin

Android specific:

• Only Android Studio's projects structure is supported

iOS specific:

• Ruby : for more info go to https://www.ruby-lang.org/en/documentation/installation/
• Xcodeproj which can be installed with $ [sudo] gem install xcodeproj. For more info go to https://github.com/CocoaPods/Xcodeproj

Please read the following assumptions carefully if you wish to use the SDK configurator for an existing project in which the Onegini SDK is already configured.

• Config model: The configurator tries to look for an existing config model class with the following name OneginiConfigModel. The location in which the SDK configurator searches is the package that is mentioned in your AndroidManifest.xml. The package can be found in the package attribute of the <manifest> element. If it cannot be found, as a second step it looks for namespace attribute in the gradle file. You must remove the existing config model if you have named it differently or if it is placed in a different location before running the SDK configurator.

• Config model: The configurator tries to look for an existing config model class in the Configuration group in the root of your Xcode project. You must remove the existing config model if it is located in a different group before running the SDK configurator.
• Certificates: [Applies only to Configurator versions up to and including 4.x.x] The configurator will remove any existing certificates located in the Resources group in the root of your Xcode project. You must remove any certificates located in another location before running the SDK configurator.

Use the --help flag for up to date help:

./sdk-configurator --help

Example for configuring an iOS project:

./sdk-configurator ios --config ~/path/to/tokenserver-app-config.zip --app-dir ~/path/to/ios-app/ --target-name myTarget --debugDetection=true --rootDetection=true -f mySubfolder

Replace the myTarget value with the application target located in your Xcode project. See the Apple documentation for more information on the app target.

Optionally use and replace mySubfolder for -f flag with proper subfolder name which is useful for many targets with different configurations each.

Example for configuring an Android project:

./sdk-configurator android --config ~/path/to/tokenserver-app-config.zip --module-name app --app-dir ~/path/to/android-app/ --debugDetection=true --rootDetection=true

Replace the app value with the name of the Gradle module that contains your application sources. See the Android documentation for more info.

The Onegini Cordova plugin contains a hook that will automatically trigger the configurator when you run cordova platform add. You can still choose to run the configurator manually (e.g. for updating an existing platform).

Example for configuring a Cordova Android project manually:

./sdk-configurator android --config /path/to/tokenserver-app-config.zip --app-dir /path/to/cordova-app/ --cordova

The Onegini NativeScript plugin contains a hook that will automatically trigger the configurator when you run tns prepare. You can still choose to run the configurator manually (e.g. for updating an existing platform).

Example for configuring a NativeScript Android project manually:

./sdk-configurator android --config /path/to/tokenserver-app-config.zip --app-dir /path/to/cordova-app/ --nativescript

Make sure you have the nativescript-onegini plugin installed before running the configurator. You will need to rerun the configurator for each installed platform in your NativeScript project.