Today, we\u2019re excited to announce the release of Auth Connect 4, Ionic\u2019s premier solution for implementing authentication in mobile applications. This release is packed full of updates, modernizing the solution as well as bringing new and highly anticipated features.<\/p>\n\n\n\n
Auth Connect exists so that teams can implement best practices in authentication across the web, Android, and iOS without having to build a manual solution. When using Auth Connect, companies can feel confident that their users are secure regardless of what platform they choose to interact on.<\/p>\n\n\n\n
Built on the widely adopted authentication standard OAuth 2.0, companies are able to quickly and easily get authentication up and running in their mobile applications and connected to their backend authentication provider. Auth Connect 4 brings all the convenience of easily implementing authentication in your application but drastically improves the developer experience across various javascript frameworks, creates a more transparent storage implementation, and now supports any authentication provider that also supports the OAuth 2.0 standard.<\/p>\n\n\n\n\n\n\n\n
Historically, building plugins to support both Capacitor and Cordova projects meant choosing to build a Cordova plugin, as it could be consumed in both Cordova and Capacitor projects. Companies, including Ionic, found this to be beneficial because it meant reaching all developers with a single project, but it came at a cost, needing to develop a Cordova plugin: brittle projects and tooling, inconsistent platform APIs, and the list goes on. Auth Connect 4 is the pioneer of a new age of plugin development that enables teams to build Capacitor plugins, enjoying the benefits of such<\/a>, while still being compatible with Cordova.<\/p>\n\n\n\n This change means that Auth Connect 4 is now built on top of Capacitor, but can be used in legacy Cordova applications for teams that still support them. This is enabled by our new Compatibility Plugin<\/a> that allows a compatible Capacitor plugin to be consumed by a Cordova plugin. This new plugin is supported as part of our open-source Capacitor project, and we highly recommend teams take advantage of it.<\/p>\n\n\n\n Previous versions of Auth Connect were class-based and very Angular-centric. However, as more teams adopt Capacitor with their preferred frameworks, such as svelte<\/a>, the class-based architecture made implementing Auth Connect a non-trivial experience. <\/p>\n\n\n\n To address this, we\u2019ve reworked Auth Connect to a new approach that is considerably more flexible and works well with any framework you might choose. Calling The returned result now contains everything your application needs to know about the user\u2019s Authentication session. You can store that and pass it to any component that needs to know, without needing to maintain a reference to a stateful class.<\/p>\n\n\n\n Auth Connect 4\u2019s transition to stateless authentication sessions leads to its next improvement, transparency with how your tokens are saved. Instead of managing the result internal to the plugin and giving you pieces of that state when asked, the relationship is inverted now. <\/p>\n\n\n\n Auth Connect gives you a serializable representation of your state and then it\u2019s up to you to store that information. Then for any subsequent requests you make using Auth Connect, you simply provide this object to the method.<\/p>\n\n\n\n You have full control over how your state is stored with your application. We recommend using Identity Vault<\/a> to securely store your tokens, protected by biometric access.<\/p>\n\n\n\n The OAuth 2.0 standard is well implemented across many different authentication providers, which provides broad compatibility for anyone looking to use Auth Connect. Unfortunately, not every aspect of how to implement this standard is explicitly defined, which can lead to small differences in how an application should talk to an authentication provider.<\/p>\n\n\n\n Auth Connect previously shipped with nearly a dozen different provider configurations, attempting to cover all of our enterprise customer\u2019s needs. Auth Connect 4 makes a major change in its approach to supporting providers. Instead of explicitly supporting various providers, it instead ships with a much more limited set of pre-defined providers and now also includes all the tools you need to completely customize how Auth Connect interacts with your provider.<\/p>\n\n\n\n If your provider allows you to send custom parameters along with the request to tweak certain behaviors, this is now entirely possible. If your provider is completely unique, you can now create a custom provider to support it. Simply extend the provided abstract A complete example of creating custom providers<\/a> can be found in our documentation. We\u2019re excited for all of the new authentication providers that Auth Connect can now easily support!<\/p>\n\n\n\n Our Auth Connect 4 upgrade guide<\/a> will walk you through exactly how to approach this upgrade and help keep the process as simple as possible. If you need help upgrading your application to the new version of Auth Connect, please reach out to Ionic Enterprise Support with any questions you may have.<\/p>\n\n\n\n Building out your authentication for your application has never been easier when you use Auth Connect. If you\u2019d like to learn more about how Auth Connect is helping other enterprises build and manage their authentication flows, reach out to sales<\/a> to schedule a private demo or try it in your app along with other Ionic native solutions with a free trial here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Today, we\u2019re excited to announce the release of Auth Connect 4, Ionic\u2019s premier solution for implementing authentication in mobile applications. This release is packed full of updates, modernizing the solution as well as bringing new and highly anticipated features. Auth Connect exists so that teams can implement best practices in authentication across the web, Android, […]<\/p>\n","protected":false},"author":86,"featured_media":5011,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"publish_to_discourse":"1","publish_post_category":"19","wpdc_auto_publish_overridden":"","wpdc_topic_tags":"","wpdc_pin_topic":"","wpdc_pin_until":"","discourse_post_id":"560385","discourse_permalink":"http:\/\/forum.ionicframework.com\/t\/announcing-auth-connect-4\/231563","wpdc_publishing_response":"success","wpdc_publishing_error":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[120,122],"tags":[156,151],"class_list":["post-5005","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-announcements","category-product","tag-auth-connect","tag-capacitor"],"acf":[],"yoast_head":"\nImproved Developer Experience<\/h2>\n\n\n\n
login<\/code> is simplified:<\/p>\n\n\n\nimport { AuthConnect } from \u2018@ionic-enterprise\/auth\u2019;\n\nconst result = await AuthConnect.login(provider, options);<\/code><\/pre>\n\n\n\nTransparent Storage<\/h2>\n\n\n\n
const result = await AuthConnect.login(provider, options);\n\nconst newResult = await AuthConnect.refreshSession(provider, result);<\/code><\/pre>\n\n\n\nSupporting Authentication Providers<\/h2>\n\n\n\n
AuthProvider<\/code> class and implement the required methods.<\/p>\n\n\n\nimport { AuthProvider } from \u2018@ionic-enterprise\/auth\u2019;\n\nexport class MyProvider extends AuthProvider {\n async authorizeRequest(...) {\n return {\n url: \u2018\u2019,\n params: {}\n }\n }\n}<\/code><\/pre>\n\n\n\nUpgrading to Auth Connect 4<\/h2>\n\n\n\n
Get Started<\/h2>\n\n\n\n