Adapter-based authentication in native Windows Phone 8 applicationsimprove this page | report issue
This tutorial illustrates the native Windows Phone 8 client-side authentication components for adapter-based authentication.
Prerequisite: Make sure that you read Adapter-based authentication first.
Creating the client-side authentication components
Create a native Windows Phone 8 application and add the MobileFirst native APIs as explained in the documentation.
CustomAdapterChallengeHandler class as a subclass of
CustomAdapterChallengeHandler class must implement the
isCustomResponsemethod checks every custom response received from MobileFirst Server to verify whether this is the expected challenge.
handleChallengemethod is called after the
Use this method to present the login form. Different approaches are available.
From the login form, credentials are passed to the
CustomAdapterChallengeHandler class. The
submitAdapterAuthentication() method is used to send input data to the authenticator.
MainPage class, connect to MobileFirst Server, register your
challengeHandler, and invoke the protected adapter procedure.
The procedure invocation triggers MobileFirst Server to send a challenge that will trigger the challenge handler.
Because the native API is not protected by a defined security test, no login form is presented during server connection.
Invoke the protected adapter procedure. The login form is presented by the
Click to download the MobileFirst project.
Click to download the Native project.
AdapterBasedAuthproject contains a MobileFirst native API that you can deploy to your MobileFirst server.
AdapterBasedAuthWP8project contains a native WP8 application that uses a MobileFirst native API library.
- Make sure to update the
worklight.plistfile in the native project with the relevant server settings.
Inclusive terminology note: The Mobile First Platform team is making changes to support the IBM® initiative to replace racially biased and other discriminatory language in our code and content with more inclusive language. While IBM values the use of inclusive language, terms that are outside of IBM's direct influence are sometimes required for the sake of maintaining user understanding. As other industry leaders join IBM in embracing the use of inclusive language, IBM will continue to update the documentation to reflect those changes.