Deploying PowerAuth Standard RESTful API Bootstrap
This chapter explains how to deploy PowerAuth Standard RESTful API.
PowerAuth Standard RESTful API is a Java EE application (packaged as an executable WAR file) responsible for exposing the RESTful API according to the specification. It exposes services for end-user applications (PowerAuth Clients), such as the mobile banking app or mobile token app.
You can use this application in case you need to use PowerAuth and cannot integrate it in your own API using our integration libraries.
Downloading PowerAuth Standard RESTful API
You can download the latest
powerauth-restful-server.war at the releases page:
Configuring PowerAuth Standard RESTful API
The default implementation of a PowerAuth Standard RESTful API has only one compulsory configuration parameter
powerauth.service.url that configures the SOAP endpoint location of a PowerAuth Server. The default value for this property points to
Setting Up Credentials
(optional) In case PowerAuth Server uses a restricted access flag in the server configuration, you need to configure credentials for the PowerAuth Standard RESTful API so that it can connect to the SOAP service:
The credentials are stored in the
Note: For SOAP interface, PowerAuth Server uses WS-Security,
UsernameToken validation (plain text password). The RESTful interface is secured using Basic HTTP Authentication (pre-emptive).
Deploying PowerAuth Standard RESTful API
You can deploy PowerAuth Standard RESTful API WAR into any Java EE container.
The default configuration works best with Apache Tomcat server running on default port 8080. In this case, the deployed server is accessible on
To deploy PowerAuth Standard RESTful API to Apache Tomcat, simply copy the WAR file in your
webapps folder or deploy it using the “Tomcat Web Application Manager” application (usually deployed on default Tomcat address
Deploying PowerAuth Standard RESTful API Outside the Container
You can also execute WAR file directly using the following command:
java -jar powerauth-restful-server.war
Note: You can overwrite the port using
-Dserver.port=8090 parameter to avoid port conflicts.