6 developer challenges solved with Mobile SDK 1.7 and OTK 4.3

Build apps faster, authenticate more securely, and support complex workflows.

Summer is here, and for many that entails a much-needed vacation or (ideally) a reduced workload. And when it comes to a hefty workload, mobile development teams come to mind as a group that is characteristically busy. Today, CA is unveiling Mobile SDK 1.7 and OAuth Toolkit 4.3, with new features that will free up time for developers – providing improved functionality and allowing for greater development flexibility.

In these releases, we have addressed 6 specific concerns that we’ve heard from our developer audience. Let’s look at a few examples.


  1. “I prefer to build apps in Xamarin.”


Many developers enjoy the cross-platform flexibility of Xamarin to write native Android and iOS apps and share code across device platforms. With developers frequently tasked with building and supporting multiple apps for multiple operating systems, Xamarin enables developers to quickly build uniform apps regardless of the platform.

Mobile SDK 1.7 will now be supported on Xamarin. This means developers can build secure iOS and Android mobile apps on an additional platform while integrating MASFoundation core functionality such as:


  • Device registration
  • User login and client credentials
  • Fingerprint session lock
  • Single Sign-On
  • Secure API access


  1. “I learn best from other developers and want to share resources in a community.”


A wide variety of mobile technologies are available today for customers to build apps, and support for our mobile SDK on Xamarin provides increased developer choice. In addition to choice, we aim to provide developers with guidance and a community of resources no matter which technology they select.

CA provides sample apps on GitHub with the latest version of our mobile SDK. SDK 1.7 is open-source-ready, platform-agnostic and available across the most popular developer platforms. By supporting the developer community, CA aims to fuel innovation and provide developers with the tools to succeed.


  1. “I want to build and integrate apps for Cordova.”


Mobile SDK 1.7 provides a command-line interface (CLI) utility, making it easier than ever to quickly build apps for Apache Cordova with the mobile SDK. With a few commands, developers can build, configure, and secure Cordova apps with CA Mobile API Gateway, as well as integrate them into their own build tools. The CLI utility provides a concise and powerful tool for app development. To further developer collaboration, it is available open source and via GitHub.


  1. “My app needs a more secure client authentication method.”


OAuth Toolkit 4.3 provides support for client authentication using a JWT (JSON Web Token), in addition to authentication with ClientID and secret, to adhere to OAuth 2.0 extension and OpenID Connect specifications. App developers can select how the application will be authenticated during client registration. JWT client authentication is generally more secure than client secret – for example, the threat of replay attack can be minimized with this method. JWT client authentication is required by OpenID Financial API (FAPI), which aims to create open standards and innovation in the fintech space.


  1. “My API and app need a fast and secure way to validate access tokens without calling the authorization server.”


OAuth Toolkit 4.3 provides support for access tokens as JWT to meet increasing requests from our customers. When OTK 4.3 issues access tokens as JWT, it allows the client and API to inspect and validate the token without additional calls to the issuing server, which can improve app performance. OTK Admin can customize claims in JWT to provide more information so that the API can deliver granular access control using this information. Additionally, authentication is backwards compatible to configure and validate simple string and JWT access tokens.


  1. “I need compatibility with a Cassandra database to support multiple apps.”


Many companies use Cassandra to manage large amounts of data across multiple servers or data centers. Netflix, for example, uses Cassandra as its back-end database for streaming services. The database’s structure creates no single point of failure and thus many enterprises deploy this type of database in their organizations.

Developers sought the ability to manage multiple client apps when connecting to Cassandra data sources, as they could with MYSQL or Oracle databases. OTK 4.3 enables this compatibility, as well as fixes a Cassandra pagination defect to achieve feature parity between OAuth clients, keys, and tokens pages for Cassandra, MYSQL, and Oracle.

For more information please visit CA for Developers.

Charlotte O'Donnelly
Charlotte is a Product Marketing Manager at CA, responsible for the go-to-market strategy for CA…


Modern Software Factory Hub

Your source for the tips, tools and insights to power your digital transformation.
Read more >
Low-Code Development: The Latest Killer Tool in the Agile Toolkit?What Are “Irresistible” APIs and Why Does Akamai's Kirsten Hunter Love Them?Persado's Assaf Baciu Is Engineering AI to Understand How You Feel