Yes it come with auto-signed certificate, and it works well with that, but i have my own certificate and i would like to use it !
the docker/aerogear documentation (https://hub.docker.com/r/aerogear/unifiedpush-wildfly/) say  : 

Note: The image will run SSL by default with self signed certificates being automatically generated.
If you want to use your own certificate and key (authority certified certificates for example), proceed as follows :
  1. put your key and certificate respectively named privatekey.key and certificate.crt in a dedicated directory.
  2. Launch the container as above but adding a volume option : -v <path to the dir where you put key and cert>:/keys
The image will use your certificates instead of the self signed ones.

as i said, the -v does not work, is there a workaround to include its own cert ?
 


2017-06-19 16:52 GMT+02:00 Matthias Wessendorf <matzew@apache.org>:
hrm, isnt that all automatically using self signed certs?

We could look at Lets Encrypt. Interested? :-)

On Mon, 19 Jun 2017 at 12:54, francoisb <francois@billard.me> wrote:
thank you Matt,
but how do you specify certificat directory with docker-compose ?

2017-06-19 11:17 GMT+02:00 Matthias Wessendorf [via aerogear-users] <[hidden email]>:
puh, this is weird.

I am actually not sure why you are facing that error. 

would you mind trying one of these compose files, instead:

that one uses a released version of the UPS, not the master branch (like the -dev does)

HTH,
Matthias

On Mon, Jun 19, 2017 at 12:11 AM, francoisb <[hidden email]> wrote:
Hi,

i am following the docker version at
https://github.com/jboss-dockerfiles/aerogear/tree/master/wildfly/unifiedpush-wildfly-dev

all is fine ! except when i add a directory that include my certificate and
my private key, wildfly fail and exit(1), here is my command  with the
result :

# docker run --name ups --link unifiedpushDB:unifiedpush --link
keycloakDB:keycloak -p 8443:8443 -it aerogear/unifiedpush-wildfly -v
/opt/ssl:/keys
Starting Liquibase migration
Liquibase Update Successful
*no /keys* directory found, will used default selfsigned certificate
=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /opt/jboss/wildfly

  JAVA: /usr/lib/jvm/java/bin/java

  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M
-XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

21:19:30,937 INFO  [org.jboss.modules] (main) JBoss Modules version
1.5.2.Final
WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)
21:19:31,045 FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with
exit code 1

--
In fact, whatever folders i specify, it fails ..
any tips or workaround ?


regards,
Francois



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Adding-certificate-folder-fails-tp1125.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list

_______________________________________________
Aerogear-users mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/aerogear-users



If you reply to this email, your message will be added to the discussion below:
http://aerogear-users.1116366.n5.nabble.com/Adding-certificate-folder-fails-tp1125p1127.html
To unsubscribe from Adding certificate folder fails, click here.
NAML



View this message in context: Re: [Aerogear-users] Adding certificate folder fails
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
Aerogear-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users
--
Sent from Gmail Mobile

_______________________________________________
Aerogear-users mailing list
Aerogear-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users