Skip to content

Architecture Overview

Juraj Ďurech edited this page May 14, 2019 · 9 revisions

PowerAuth Cryptography documentation has been moved to: https://developers.wultra.com/docs/develop/powerauth-crypto/Architecture-Overview

Please use the new developer portal to access documentation.


PowerAuth 2.0 architecture is designed so that the deployment can be very simple, but at the same time allows complex deployment alongside of other authentication methods (as a part of the central authentication / authorization component).

Architecture Diagram

Following diagram captures the basic deployment strategy for the PowerAuth 2.0 technology.

Architecture Overview

As you can see, there are only couple components present:

  • Our back-end components
  • Your existing back-end components
  • Our integration libraries for your back-end components
  • Our mobile SDK for iOS and Android apps

Our Back-End Components

PowerAuth 2.0 Deplyment requires installation of just one easy to deploy component.

  • PowerAuth 2.0 Server
    • The core server component that manages activated devices, enables the activation process, verifies signatures and keeps system configuration.
    • Component communicates using SOAP or REST services.
    • Documentation:
  • PowerAuth 2.0 Admin (optional)

Your Back-End Components

PowerAuth 2.0 instalation has impact on several of your components:

  • Mobile Banking API application - Application that publishes API that is consumed by the mobile clients.
  • Activation Channels - Various types of applications used to activate PowerAuth 2.0 Client, for example the internet banking, ATM interface, branch applications, etc.
  • Internal bank systems / ESB - Of course, you can use any systems to proxy PowerAuth 2.0 Server services.

Our Back-End Integration Libraries

To simplify deployment, PowerAuth 2.0 brings ready-to-use libraries for Java EE / Spring, namely:

Our Mobile SDK for iOS or Android

You can integrate PowerAuth 2.0 easily with your mobile app using our high-level SDK.