Microsoft Azure Active Directory Authentication Library (ADAL) is a framework designed to make secured resources available to apps via security tokens. Apps integrated with ADAL can share authentication state enabling seamless SSO (Single Sign-On) capabilities.
This Knowledge Base article provides the steps to add Microsoft ADAL to any mobile Android or iOS app.
We hope you find it useful and enjoy using Appdome!
Adding Microsoft ADAL to Mobile Apps Fast
Appdome is a mobile integration platform as a service (iPaaS) that allows users to add a wide variety of features, SDKs and APIs to Android and iOS apps. Using a simple ‘click to add’ user interface, Appdome allows anyone to easily integrate Azure AD SSO to any mobile app – instantly, no code or coding required.
Using Appdome, there are no development or coding prerequisites. For example, there is no Appdome SDK, libraries, or plug-ins to implement. Likewise, there are no required infrastructure changes and no dependency on SAML, OAuth, OpenID Connect or any other authentication standard inside the app. Users merely upload mobile apps, select the Azure AD service and click “Fuse My App.” The Appdome technology adds Azure AD SSO and relevant standards, frameworks and more to the app automatically, with no manual development work at all.
Using Appdome, mobile apps will use Microsoft ADAL SSO to authenticate users as if ADAL was natively coded to the app. Appdome for ADAL SSO is compatible with mobile apps built in any development environment including Native Android and iOS apps, hybrid apps and non-native apps built in Xamarin, Cordova, and React Native, Ionic and more. This streamlines implementations, cuts development work, and ensures a guaranteed and consistent integration of Microsoft ADAL SSO to any mobile app.
The following diagram illustrates the Single-Sign-On flow for apps that have been integrated with Microsoft ADAL.
Note: The flow is similar for direct and brokered authentication.
- The application sends an unauthorized request to reach a resource like internal.mycomp.com which is protected by a gateway, AD, or the app server itself.
- The server protecting the resource responds with 401 or 30X response since the request is not authorized.
- Appdome identifies the response for the protected resource and opens an internal Webview within the Fused App.
- The internal Webview is opened to the ADAL Hub URL (For example: myadal.com.com).
- The user can now authenticate using any authentication method the hub URL requires, during the authorization session, the cookies and authorization token are received.
- The Azure server redirects to the successful URI (e.g. mycomp://authorized) since the authorization succeeded. Note that the app’s Success URI is configured on Azure should match the configuration during fusion.
- Appdome identifies the successful URI redirect and closes the internal Webview, thus returning the view to the original app.
- Now, when the app tries to reach the protected resource, the authorization header or cookies are attached to the outgoing request. The gateway will trust these credentials and the app will reach the protected resource successfully.
For more information on how Appdome gets, retrieves and stores ADAL tokens in mobile apps, please review the data sheet on No Code Microsoft Authentication in Mobile Apps.
Prerequisites for using Appdome for Microsoft ADAL SSO
In order to use Appdome’s no code implementation of Microsoft ADAL SSO on Appdome, you’ll need:
- Appdome account
- Mobile App (.ipa for iOS, or .apk for Android)
- Azure Hub URL
- Authentication Successful URI for Native App
- Azure URIs for protected resources
- Azure Client ID (Application id)
- Signing Credentials (e.g., signing certificates and provisioning profile)
Log in to your Microsoft Azure portal and retrieve the Azure Client ID. If you have not yet registered an application in Azure AD, you can see How to Register Apps in Microsoft Azure Active Directory.
How to add Microsoft ADAL SSO to Any Mobile App on Appdome
Follow these step-by-step instructions to add Microsoft Adal SSO to any mobile app:
Upload a Mobile App to Your Account
From the “Fuse” tab, Add Microsoft ADAL SSO
- Select the Fuse tab. Note: a blue underline will appear showing the step is active
- Select the Authentication category. Note: a blue highlight will appear showing the category is active.
- Click + Add Profile, and select Microsoft Active Directory Authentication Library (ADAL) from the drop down menu.
- You can Add specific URLs to apply the authentication to, or leave “all” to apply to all URLs accessed by the app.
- Enter the URL for your ADAL Authority
- Enter the URI for Redirect URI
- Enter the Client ID for the app (in Azure sometimes also called Application ID)
- Optionally toggle “ON” Validate Authority
- Optionally toggle “ON” Brokered Authentication
- Click Fuse My App
The technology behind Fuse My App has two major elements – (1) a microservice architecture filled with 1000s of code sets needed for mobile integrations, and (2) an adaptive code generation engine that can recognize the development environment, frameworks and methods in each application and match the application to the relevant code-sets needed to add Microsoft ADAL SSO to the mobile app in seconds.
Congratulations! You now have a mobile app fully integrated with Microsoft ADAL SSO.
After Adding Microsoft ADAL SSO to a Mobile App on Appdome
After you have added Microsoft ADAL SSO to any mobile app on Appdome, there are a few additional steps needed to complete your mobile integration project. Please view the article here on How to Complete My Mobile Integration Project After I Fuse My App.
That is it – Enjoy Appdome for Microsoft ADAL SSO in your application!
How Do I Learn More?
Check out Microsoft documentation, Appdome for SSO+ blog or request a demo at any time.
If you have any questions, please send them our way at email@example.com or via the chat window on the Appdome platform.