Configuring Access Manager for Mobile

Use the topics in this hierarchy to configure IBM Security Access Manager for Mobile.

Configuring Access Manager for Mobile This section provides configuration procedures for IBM Security Access Manager for Mobile, including support for Oauth, one time password, and integration with WebSEAL.

Getting started with Access Manager for Mobile
Several configuration tasks must be completed in order to start using IBM Security Access Manager for Mobile.
Managing application interfaces
To manage application interfaces with the local management interface, use the Application Interfaces management page.
Managing the runtime component
To manage configuration files with the local management interface, use the Runtime Component management page.
Managing user registries
The appliance runtime profile has a user registry associated. Use the User Registry management page to administer the users and group memberships. The user registry in discussion here is the one used by the runtime applications, not the one used by the management interface.
Runtime security services external authorization service
The runtime security services external authorization service (EAS) provides the policy enforcement point function for context-based access.
Using the isamcfg tool
Various features in IBM Security Access Manager for Mobile can be configured with the isamcfg tool.
Adding runtime listening interfaces
Add your application interfaces to the list of runtime listening interfaces only if you have a deployment where Access Manager for Web and Access Manager for Mobile run on separate appliances. This configuration procedure enables communication between the two appliances.
Support for compliance with NIST SP800-131a
IBM Security Access Manager for Mobile 8.0 supports the requirements that are defined by the National Institute of Standards and Technology (NIST) Special Publications 800-131a.
Authentication
Security Access Manager provides user authentication functions that allow for simple and complex authentication scenarios.
OAuth 2.0 support
IBM Security Access Manager for Mobile supports the OAuth 2.0 protocol. The implementation of OAuth 2.0 in Security Access Manager for Mobile strictly follows the OAuth 2.0 standards.
Managing advanced configuration
Adjust configuration settings in supported configuration files.
Deploying pending changes
Some configuration and administration changes require an extra deployment step.
Tuning runtime application parameters and tracing specifications
To manually tune selected runtime application parameters and tracing specifications, use the Runtime Parameters management page.
Options for handling session failover events
Security Access Manager for Mobile offers several solutions to the challenge of providing sharing of session state across multiple servers in a clustered environment.
JavaScript whitelist
IBM® Security Access Manager for Mobile JavaScript mapping rules call Java™ code from JavaScript. The set of classes that can be called are restricted.

Parent topic: Configuring