Learn how to pass SSO authentication cookies to all domains in any Android and iOS app. Appdome makes it easy to implement mobile SSO in any app without coding.
Tokens received from authentication are generally associated with the specific domains from which they were received. In cases when the authentication domain is different than that of the protected resource – tokens might not be associated with the protected resource.
Applications might, in several scenarios, need the ability to propagate authentication cookies to all domains.
This Knowledge Base article provides step-by-step instructions for using Appdome to propagate SSO cookies to all domains within any Android and iOS mobile app.
We hope you find this knowledge base useful and enjoy using Appdome!
Appdome is a no-code mobile app security platform designed to add security features in mobile apps.
Appdome’s no-code mobile app security platform offers mobile developers, DevSec and security professionals a convenient and reliable way to protect Android and iOS apps without coding. When a user clicks “Build My App,” Appdome leverages a microservice architecture filled with 1000s of security plugins, and an adaptive code generation engine that matches the correct required plugins to the development environment, frameworks, and methods in each app.
Using Appdome, there are no development or coding prerequisites to build secured apps. There is no SDK and no library to manually code or implement in the app. The Appdome technology adds the relevant standards, frameworks, stores, and logic to the app automatically, with no manual development work at all.
Likewise, there are no required infrastructure changes and no dependency on SAML, OAuth, OpenID Connect or any other authentication standard inside the app. The Appdome technology can propagate SSO cookies to all domains and more to the app automatically, with no manual development work at all. Using Appdome, mobile apps will be able to propagate SSO cookies as if it was natively coded to the app.
As part of defining the organization’s authentication infrastructure, you would like to protect certain resources that mobile apps might need to use and limit the access to those resources by having the user authenticate with one of the SSO providers or supported protocols. The application then needs to go through authentication when it tries to access a protected resource. After authenticating the application receives a token with which it can authenticate further, without the need for user interaction, until the token expires. This means that after authentication, the token needs to be passed along with requests the Application makes for the resource.
Appdome allows you to easily choose the authentication provider/scheme and define which resources should be protected. Once the application is built the authenticator will be activated automatically when needed and the token will be managed by Appdome and passed to requests as needed. Furthermore, Appdome will automatically recognize when the token has expired and will require authentication again.
In order to use Appdome’s no code Cookies Groups on Appdome, you’ll need:
Follow these step-by-step instructions to add Cookies Groups to any mobile Application:
Beneath the Build Tab, you will find several service options. Select Authentication. Note: a blue highlight will appear showing the category is active.
4. When finished, click Build My App.
The technology behind Build 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 Cookies Groups to the mobile app in seconds.
Congratulations! You now have a mobile app fully integrated with Cookies Groups.
After you have added Cookies Group so any mobile app on Appdome, there are a few additional steps needed to complete your mobile integration project.
Appdome is a full-featured mobile integration platform. Within Context™, Appdome users can brand the application, including adding a favicon to denote the new service added to the application.
For more information on the range of options available in Context™, please read this knowledge base article.
In order to deploy an Appdome-built app, it must be signed. Signing iOS app and Signing an Android app are easy using Appdome. Alternatively, you can use Private Signing, download your unsigned app and sign locally using your own signing methods.
Once you have signed your Appdome-built app, you can download to deploy it using your distribution method of choice. For more information on deploying your Appdome-built apps, please read this knowledge base.
That is it – Enjoy Appdome for Cookies Groups in your application!
To zoom out on this topic, visit Appdome for Mobile Identity on our website.
If you have any questions, please send them our way at firstname.lastname@example.org or via the chat window on the Appdome platform.
Thanks for visiting Appdome! Our mission is to make mobile integration easy. We hope we’re living up to the mission with your project. If you don’t already have an account, you can sign up for free.