Note: For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.
Remotely disabling application access to protected resources
Learn how to remotely disable an application and deny it access to protected resources due to phase-out policy or identified security issues.
About this task
Use MobileFirst Operations Console (the console) to disable user access to a specific version of an application on a specific mobile operating system, and provide a custom message to the user.
Procedure
Results
When a user runs an application that was remotely disabled,
a dialog window with your custom message is displayed. The message
is displayed on any application interaction that requires access to
a protected resource, or when the application tries to obtain an access
token. If you provided a version-upgrade URL, the dialog has a Get
new version button for upgrading to a newer version, in
addition to the default Close button. If the
user closes the dialog window without upgrading the version, they
can continue to work with the parts of the application that do not
require access to protected resources. However, any application interaction
that requires access to a protected resource causes the dialog window
to be displayed again, and the application is not granted access to
the resource.
Note: For cross-platform applications,
you can customize the default remote-disable behavior: provide an
upgrade URL for your application, as outlined in Step 3, and set the showCloseOnRemoteDisableDenial attribute
in your application's initOptions.js file to false.
If the attribute is not defined, define it. When an application-upgrade
URL is provided and the value of showCloseOnRemoteDisableDenial is false,
the Close button is omitted from the remote-disable
dialog window, leaving only the Get new version button.
This forces the user to upgrade the application. When no upgrade URL
is provided, the showCloseOnRemoteDisableDenial configuration
has no effect, and a single Close button is
displayed.