diff --git a/docs/Installing-Bouncy-Castle.md b/docs/Installing-Bouncy-Castle.md index 366d41188..8b5b31970 100644 --- a/docs/Installing-Bouncy-Castle.md +++ b/docs/Installing-Bouncy-Castle.md @@ -19,7 +19,7 @@ Java 11 no longer provides a library extension mechanism and thus Bouncy Castle #### Bouncy Castle on Tomcat -Copy [`bcprov-jdk18on-172.jar`](https://mvnrepository.com/artifact/org.bouncycastle/bcprov-jdk18on) to your `${CATALINA_HOME}/lib` folder. +Copy [`bcprov-jdk18on-176.jar`](https://mvnrepository.com/artifact/org.bouncycastle/bcprov-jdk18on) to your `${CATALINA_HOME}/lib` folder. Bouncy Castle library will not work properly in case any war file deployed to Tomcat contains another copy of the Bouncy Castle library, even if the war file is not related to PowerAuth. @@ -28,7 +28,7 @@ Bouncy Castle library must be only present in the `${CATALINA_HOME}/lib` folder. #### Bouncy Castle on JBoss / Wildfly -PowerAuth server requires a specific version of Bouncy Castle library: `bcprov-jdk18on-172.jar` +PowerAuth server requires a specific version of Bouncy Castle library: `bcprov-jdk18on-176.jar` In order to make PowerAuth Server work on JBoss / Wildfly, you need to add and enable the external Bouncy Castle module on the server by adding the `` element in the `standalone.xml` file: @@ -46,12 +46,12 @@ The module should be defined using a new module XML file in JBoss folder `module - + ``` -Finally, copy the Bouncy Castle library `bcprov-jdk18on-172.jar` into folder `modules/system/layers/base/org/bouncycastle/external/main` so that it is available for the module. +Finally, copy the Bouncy Castle library `bcprov-jdk18on-176.jar` into folder `modules/system/layers/base/org/bouncycastle/external/main` so that it is available for the module. Do not reuse Bouncy Castle module `org.bouncycastle` from JBoss, because version of library provided by JBoss may differ from version required by PowerAuth. @@ -82,7 +82,7 @@ Java 8 provides a library extension mechanism which can be used to installed Bou ##### Standalone Tomcat -When running a standalone Tomcat instance, all you need to do is to copy [`bcprov-jdk18on-172.jar`](https://mvnrepository.com/artifact/org.bouncycastle/bcprov-jdk18on) to your `${JDK_HOME}/jre/lib/ext` folder. +When running a standalone Tomcat instance, all you need to do is to copy [`bcprov-jdk18on-176.jar`](https://mvnrepository.com/artifact/org.bouncycastle/bcprov-jdk18on) to your `${JDK_HOME}/jre/lib/ext` folder. ##### Embedded Tomcat @@ -96,7 +96,7 @@ Make sure to add the provider to the top of the list (ideally, N=2). #### Bouncy Castle on JBoss / Wildfly -PowerAuth server requires a specific version of Bouncy Castle library: `bcprov-jdk18on-172.jar` +PowerAuth server requires a specific version of Bouncy Castle library: `bcprov-jdk18on-176.jar` In order to make PowerAuth Server work on JBoss / Wildfly, you need to add and enable the external Bouncy Castle module on the server by adding the `` element in the `standalone.xml` file: @@ -114,12 +114,12 @@ The module should be defined using a new module XML file in JBoss folder `module - + ``` -Finally, copy the Bouncy Castle library `bcprov-jdk18on-172.jar` into folder `modules/system/layers/base/org/bouncycastle/external/main` so that it is available for the module. +Finally, copy the Bouncy Castle library `bcprov-jdk18on-176.jar` into folder `modules/system/layers/base/org/bouncycastle/external/main` so that it is available for the module. Do not reuse Bouncy Castle module `org.bouncycastle` from JBoss, because version of library provided by JBoss may differ from version required by PowerAuth. diff --git a/powerauth-java-server/src/main/webapp/WEB-INF/jboss-deployment-structure.xml b/powerauth-java-server/src/main/webapp/WEB-INF/jboss-deployment-structure.xml index 45f68d9cf..92574b588 100644 --- a/powerauth-java-server/src/main/webapp/WEB-INF/jboss-deployment-structure.xml +++ b/powerauth-java-server/src/main/webapp/WEB-INF/jboss-deployment-structure.xml @@ -12,7 +12,7 @@ - +