Challenge handling in a gateway topology
Learn about special challenge-handling considerations when using a gateway between a client application and MobileFirst Server.
When access to MobileFirst Server is protected by a security gateway, a challenge is sent for any client attempt to access a server endpoint, except for pre-approved endpoints. This rule is true also for the client's initial request to register with the server. However, because the registration stage is executed entirely in the native environment, only a challenge handler that is implemented and registered in native code is called during the client's registration. A challenge handler that is implemented and registered in cross-platform JavaScript code is not called during client registration.
To allow a hybrid
application to handle challenges during its registration with the
server, follow these steps to register a native challenge handler
from the application's native environment:
Note: The examples are for
a MyHybridApp MobileFirst hybrid
application with a native iPhone environment that uses the default
startup process (see MobileFirst Default startup process in iOS-based hybrid applications).