Set the App SDK version number in your app's config.js file to "9.1.0".
If you defined a custom class that implemented a Live Data interface, your custom class should also implement the corresponding Base View interface:
Live Data interface | Base View interface |
|---|---|
| |
| |
| |
| |
| |
In order to make your custom view implementation available to the SDK, define a custom class that implements the createView() method of the corresponding UI Factory base class. Your application then calls the setInstance() static method of the corresponding UI Factory base class during application initialization and provides an instance of your custom UI factory implementation.
Base View interface | UI Factory base class |
|---|---|
| |
| |
| |
| |
| |
See the corresponding subsection of Replacing the UI section for more details.
AdaptiveAuthenticationView.enable() is replaced by DefaultAdaptiveAuthenticationView.enable(). Modify your application to call BaseAdaptiveAuthenticationView.getController().enable() instead. Your deprecated call to AdaptiveAuthenticationView.enable() will continue to run but it uses the default implementation of enable() that is defined in class DefaultAdaptiveAuthenticationView.
SuggestRegistrationView.enable() is replaced by DefaultSuggestRegistrationView.enable(). Modify your application to call BaseSuggestRegistrationView.getController().enable() instead. Your deprecated call to SuggestRegistrationView.enable() will continue to run but it uses the default implementation of enable() that is defined in class DefaultSuggestRegistrationView.
The listener parameter to the BaseFidoRegistrationView.show() method is deprecated. Call view.getController().setListener() to set the listener instead. Note that the return type of AppSdk.getFidoRegistrationView() is changed from class FidoRegistrationView to interface BaseFidoRegistrationView.
If your application implements the ISessionNotification interface, update its onRenewSession() method to resolve the returned Promise with a SessionData object instead of an expiration timestamp. The SessionData object must have sessionKey and exp fields containing the new session key and expiration timestamp in seconds from epoch. See Managing Session Renewal and Expiration Time.
If your application calls NNLSessionManager.initialize() with a custom configuration, make the following changes to the second parameter configuration:
Remove timeoutOffset and renewThreshold.
Rename idleTimeout to sessionLifetime. Note: sessionLifetime has a default value of 1800.
The App SDK now calculates a default value for renewalInterval if it is not specified. Specifying renewalInterval does not override the other fields inside configuration.
See Client API Docs for NNLSessionManager class for more details.
If your application relies on the sessionData.sessionKey property returned after a successful transaction, please note that the following APIs no longer return a sessionKey in the resolved sessionData:
AdaptiveUI.transact()
AdaptiveUI.getAuthenticationView() when called with a transactionID