Add bank-grade mobile security to your iOS, tvOS, watchOS and Android apps with the PowerAuth Mobile SDK. It is the client-side part of Wultra's Mobile-First Authentication and the PowerAuth platform. It takes care of the demanding network and cryptographic processes behind secure device activation, request signing and strong customer authentication, so you can ship a secure, frictionless user experience faster, with no need to build your own security layer.
- Upgrading to Post-Quantum Cryptography
- Differences Between Android and iOS
- Implementing Secure PIN Keyboard
- Working With Activation Status
If you need to upgrade PowerAuth Mobile SDK to a newer version, you can check the following migration guides:
- Migration from version
2.0.xto2.1.x - Migration from version
1.9.xto2.0.x - Migration from version
1.8.xto1.9.x - Migration from version
1.7.xto1.8.x - Migration from version
1.6.xto1.7.x - Older Migration Guides
| Mobile SDK | Protocol | PowerAuth Server | Support Status |
|---|---|---|---|
2.1.x |
V4.0 or V3.3 |
2.0+ or 1.9+1 |
Fully supported |
2.0.x |
V4.0 or V3.3 |
2.0+ or 1.9+1 |
Fully supported |
1.9.x |
V3.3 |
1.9+ |
Security & Functionality bugfixes |
1.8.x |
V3.2 |
1.5+ |
Security bugfixes |
1.7.x |
V3.1 |
0.24+ |
Security bugfixes |
1.6.x |
V3.1 |
0.24+ |
Not supported |
Note 1: Protocol and server compatibility depend on the SDK configuration. If you choose to remain on protocol V3.3, PowerAuth Server version 1.9+ is required.
All sources are licensed using Apache 2.0 license, you can use them with no restriction. If you are using PowerAuth 2.0, please let us know. We will be happy to share and promote your project.
If you need any assistance, do not hesitate to drop us a line at hello@wultra.com.
If you believe you have identified a security vulnerability with PowerAuth, you should report it as soon as possible via email to support@wultra.com. Please do not post it to a public issue tracker.