Download Latest Version ebics-server-alpha.jar (2.3 MB)
Email in envelope

Get an email when there's a new version of EBICS server

Home
Name Modified Size InfoDownloads / Week
readme.txt 2014-04-16 5.0 kB
ebics-server-alpha.jar 2014-04-16 2.3 MB
Totals: 2 Items   2.3 MB 0
this ebicsserver is an implementation of the EBICS protocol (http://www.ebics.org/) writed in java with open jdk 7

It's serve page on the local machine on the port 8080.
Example url : https://localhost:8080/

FEATURES
--------

Actual version support :
- H003 protocol  HEV / INI / HIA / HPB / HPD / FUL / FDL  / HCS / PUB / HCA request's
- H004 protocol HEV / INI / HIA / HPB/ HPD   
- multiple host (enabled by default in config.xml)
- Two host's engine

ENGINES :
----------
  
* EBICSQualifHost

The "EBICSQualifHost" class is an ebics server which accept any HOSTID / PARTNERID / USERID.

This alpha version of EBICSQualifHost store files on ~/.ebicsserver/
All request are logged into  ~/.ebicsserver/logs/

uploaded file are stored into ~/.ebicsserver/$HOSTID/$PARTNERID/$FILEFORMAT or if testmode is TRUE ~/.ebicsserver/$HOSTID/$PARTNERID/test/$FILEFORMAT, only file in the first directory can be downloaded.

The certificates and private key of the server are persistent and stored in ~/.ebicsserver/$HOSTID/config.xml, they are generated on the first host's access 
The certificates send by user are not persistent, the INI/HIA should be send at each restart of the server.

* EBICSQualifHostCfg

The "EBICSQualifHostCfg" class is an ebics server which accept only  PARTNERID / USERID defined in the configuration file.
The certificates and private key of the server are persistent and stored in ~/.ebicsserver/config.xml, they are generated on the first host's access 
The certificates send by user, and the user state are persistent and stored in config.xml.

Example config.xml file for one host (certificate's data and private key's data are truncated):

<?xml version="1.0" encoding="UTF-8"?>
<config>
  <core>
    <autoCreateHost>false</autoCreateHost>
    <hostDefaultClass>ebics.server.qualif.EBICSQualifHost</hostDefaultClass>
  </core>
  <https>
    <port>8080</port>
  </https>
  <hosts>
    <host class="ebics.server.qualif.EBICSQualifHostCfg" id="QUALIF">
      <!-- 
 		autoValidateCertificates determine if the user's state is set to ready automatically 
 		after the reception of HIA 
      -->
      <autoValidateCertificates>true</autoValidateCertificates>	
      <Institute>My Institute</Institute>
      <DownloadableOrderData>false</DownloadableOrderData>
      <PreValidationSupport>true</PreValidationSupport>
      <events>
      	<event id="onUploadComplete">shellscript.sh $FILE</event>
      	<event id="onDownloadComplete">shellscript.sh $FILE</event>
      </events>
      <partners>
        <partner id="PARTNER1">
          <events>
      	     <event id="onUploadComplete">shellscript.sh $FILE</event>
      	     <event id="onDownloadComplete">shellscript.sh $FILE</event>
          </events>
          <users>
            <user id="USER1">
              <sign>
                <certificate>MIIDxjCCAq ... ziekg==</certificate>
              </sign>
              <auth>
                <certificate>MIIDxjCCAq ... ziekg==</certificate>
              </auth>
              <crypt>
                <certificate>MIIDxjCCAq ... ziekg==</certificate>
              </crypt>
              <ready>true</ready>
              <signVers>A005</signVers>
              <authVers>X002</authVers>
              <cryptVers>E002</cryptVers>
            </user>
          </users>
        </partner>
        <partner id="PARTNER2"/>
      </partners>
      <auth>
        <certificate>MIIC3DC  ... J9ro1Q==</certificate>
        <privatekey>MIIEvQIB ... Q5N+s=</privatekey>
      </auth>
      <crypt>
        <certificate>MIIC3 ... +AQ==</certificate>
        <privatekey>MIIEwA ... Zx/I=</privatekey>
      </crypt>
    </host>
  </hosts>
</config>

 

BUILD
-----

- through eclipse ( eclipse configuration is in SVN )
- or for deploying on servers, there is a script build.sh


Keystore setting
----------------

The internal https server, needs a keystore  searched in :

~/.ebicsserver/.keystore

how to create this file :

~$ keytool -genkey -alias 192.168.10.11 -keyalg RSA -keystore .ebicsserver/.keystore -keysize 2048
Entrez le mot de passe du fichier de clés : ebicsserver 
Ressaisissez le nouveau mot de passe : ebicsserver
Quels sont vos nom et prénom ?
  [Unknown]:  ebicsserver
Quel est le nom de votre unité organisationnelle ?
  [Unknown]:  ebicsserver
Quel est le nom de votre entreprise ?
  [Unknown]:  ebicsserver
Quel est le nom de votre ville de résidence ?
  [Unknown]:  Paris
Quel est le nom de votre état ou province ?
  [Unknown]:  FR
Quel est le code pays à deux lettres pour cette unité ?
  [Unknown]:  FR
Est-ce CN=ebicsserver, OU=ebicsserver, O=ebicsserver, L=Paris, ST=FR, C=FR ?
  [non]:  oui

Entrez le mot de passe de la clé pour <192.168.10.11>
        (appuyez sur Entrée s'il s'agit du mot de passe du fichier de clés) :  
Ressaisissez le nouveau mot de passe :


Configuration File :

On the first execution of the server the default configuration file is writed in :
~/.ebicsserver/config.xml

Restart of the server is needed if config.xml is externally modified.


Source: readme.txt, updated 2014-04-16