When using the MAG SDK on Android, specifically, does the sdk require that the user configures the device PIN/pattern beforehand in order to take advance of the lock-device in-built capability? If they don't will the SDK continue to function, but locking will fail or th euser will get a warning?
On the initial run of the app the user should be notified that a PIN is required.
So in this instance, the MAG SDK will block until the user has configured a pin or pattern on Android - is this correct? If the developer decides not to utilise App locking with the SDK, then will it continue to block on the initial run
I don't believe it blocks it entirely, it allowed me to cancel out of the dialog so guessing you would just have issues using storage API's if not enabled. It is required to utilize MAS local storage.
If you have devices where PIN/lock security is not available, you can use Account Manager Storage (AMS) as an alternative to using Android KeyStore for token storage.
Android Guides | CA Mobile App Services
It seems that the Mobile SDK is designed to force the use of the device lock, which is exactly what they want to avoid. They want the Android SDK to work regardless if the device lock pin/pattern is set or not. Can we turn off any warning, programmatically if the device lock is not configured?
You mention "so guessing you would just have issues using storage API's if not enabled" - can I get a definite answer on this please - does this mean the SDK for device registration, SSO and API invocation will not work.
More information about AccountManager Storage can be found under Android Guides | CA Mobile App Services
All functionality on the SDK will work the same as using Android KeyStore, the AMS supports SSO, device registration, API invocation, etc...