Activity for Javier Munoz
-
Javier Munoz posted a comment on discussion Help
Excellent! Inside the container there are 2 volumes you need to map. "/usr/src/openas2/Runtime/config" for configuration files "/usr/src/openas2/Runtime/data" for data files Also 2 exposed container Ports which are: 10080 for AS2 receiving 10081 for MDN receiving For example. you could run your container like: docker run -it -v $(pwd)/config:/usr/src/openas2/Runtime/config -v $(pwd)/data:/usr/src/openas2/Runtime/data -p4080:10080 -p4081:10081 openas2
-
Hi Aamir, I made the Dockerfile script. I uploaded a Docker container to Dockerhub https://hub.docker.com/repository/docker/greicodex/openas2
-
Also please list the packages you have on your Server installation. The following dependencies were included in the POM.XML to address that situation: <dependency> <groupid>javax.xml.bind</groupid> <artifactid>jaxb-api</artifactid> <version>2.2.11</version> </dependency> <dependency> <groupid>com.sun.xml.bind</groupid> <artifactid>jaxb-core</artifactid> <version>2.2.11</version> </dependency> <dependency> <groupid>com.sun.xml.bind</groupid> <artifactid>jaxb-impl</artifactid> <version>2.2.11</version>...
-
API Response 401 corresponds the status "Unauthorized". Make sure you have the correct username/password. API response 500 corresponds to the status "Internal Server Error". According to the log you are missing a MediaBodyWriter for JSON. That most likely is a J2EE package that could be missing from your installation (JAXB). Oracle removed the J2EE packages from their download for Java 9+ Which Java version are you using? On Wed, Apr 8, 2020 at 8:42 AM Gabe gabesource@users.sourceforge.net wrote:...
-
Yes, you can do that. Since the certificate is set to the domain name, and you are using SSL in the config.xml base uri, the URL parameter on the login should also match. -J On Tue, Apr 7, 2020 at 9:36 AM Gabe gabesource@users.sourceforge.net wrote: Hello, My DNS is set up, I can access my server using the domain name. My question is on the login screen of the API REST, it's default parameter is "https://127.0.0.1:8443/api". Maybe I should use my domain instead ? I have try to change it in the "config.xml"...
-
Yes, it seems like. The REST API included in OpenAS2 has an open CORS policy enabled since its password protected. From the log extract seems like you are hosting the WebUI application on the custom test domain myserver.mydomain.com. The instructions provided on the README.md file are for localhost testing and development. The error you get is from the application trying to establish a Websocket connection to the localhost environment for debugging. Since you are not looking to develop the WebUI...
-
Hi, In order to better trace the issue. Could you open up the Chrome Developer tools or the Firefox Dev Console and share your Javascript Console logs with me? Regards, J On Mon, Mar 30, 2020 at 3:43 AM Gabe gabesource@users.sourceforge.net wrote: Hello, Yes the keystore was cleaned before I added my wildcard certificate (3rd party CA signed), and the intermediate and the root certificates. I have also checked that my new keystore password was the good one. And I have already succesfully exchange...
-
The certificate is in config/ssl_certs.jks, Is your own certificate loaded into it? Is it self-signed as well or 3rd party CA signed? Did you remove the Old OpenAS2 self-signed certificate? Regards, J On Fri, Mar 27, 2020 at 7:18 AM Gabe gabesource@users.sourceforge.net wrote: Hello, Many thanks for you explanations, the server is running now : yarn run serveINFOS: Started listener bound to [localhost:8443] Is the self-signed certificate is in the "config/ssl_certs.jks" file ? Because I have updated...
-
Hi Gabe, Agreed the documentation for the WebUI is lacking, we are working on that. With the WebUI inclusion into OpenAS2 a REST API was added and exposed as a new Remote Control interface for OpenAS2. This remote interface needs to be habilitated by adding the "org.openas2.cmd.processor.RestCommandProcessor" Command processor in to the config.xml file of your OpenAS2 Server installation. The default configuration included in your latest download of OpenAS2 includes a basic configuration of this...
-
Hi Gabe, Agreed the documentation for the WebUI is lacking, we are working on that. With the WebUI inclusion into OpenAS2 a REST API was added and exposed as a new Remote Control interface for OpenAS2. This remote interface needs to be habilitated by adding the "org.openas2.cmd.processor.RestCommandProcessor" Command processor in to the config.xml file of your OpenAS2 Server installation. The default configuration included in your latest download of OpenAS2 includes a basic configuration of this...
-
Hi Gabe, Agreed the documentation for the WebUI is lacking, we are working on that. With the WebUI inclusion into OpenAS2 a REST API was added and exposed as a new Remote Control interface for OpenAS2. This remote interface needs to be habilitated by adding the "org.openas2.cmd.processor.RestCommandProcessor" Command processor in to the config.xml file of your OpenAS2 Server installation. The default configuration included in your latest download of OpenAS2 includes a basic configuration of this...
-
Hi Gabe, Could you share the console logs and the configuration files you are using? Is this error happening on a new installation or an upgrade? -J
1