Build, protect and deploy apps across any platform and mobile device
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate decision processes with a no-code business rules engine
Build mobile apps for iOS, Android and Windows Phone
Deploy automated machine learning to accurately predict machine failures with technology optimized for Industrial IoT.
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
With the GA of OpenEdge 11.2 now successfully behind us, it’s time to take a closer look at one of the “mega topics” that (almost) everyone is talking about – security and mobile apps. In this two part series, we’ll first take a closer look at security from the mobile client perspective. In part two, we’ll dive into security requirements at the Web and Application Server Tier and explore the capabilities of the OpenEdge platform and how it satisfies those requirements to provide a secure, end-to-end deployment platform for mobile apps. I hope this proves useful for the broader OpenEdge Community, and not just Alice and Bob….
Illustration 1. A mobile native app running inside a native wrapper for the target platform (iOS and/or Android)
Anonymous – basically establish a session without supplying user credentials
Clearly, these authentication models have to match across the mobile app and mobile application – i.e. Web Tier components of the architecture. Progress supplies mobile application security templates for appropriately locking down resources on the Web Tier (but we’ll look at that at more depth in part two).
That’s it for this brief tour of client-side security in OpenEdge Mobile. Watch this space for part two where we’ll look at more depth in securing the Web and Application Server components of our Mobile Application architecture.
Gary is responsible for developing go-to-market strategies, providing technical marketing support and developing best practice materials for the Rollbase aPaaS platform.
Copyright © 2017 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.