This procedure describes how to create a new bank in EBICS Server with generated key pairs for encryption and authentication.
| Field | Description |
|---|---|
| Name | Enter a unique name that is used to identify a bank at various points in the administration interface. |
| Host ID | Enter the bank EBICS identifier. |
| Long IDs | Select this option to activate the use of the updated EBICS 2.4 standard for character length. |
| EBICS support | Select this option to enable EBICS support for the new bank. |
| EBICS Host-ID | Enter the bank EBICS identifier. |
| URL |
Enter https://<hostname>:<port>/ebics/EbicsServlet Where <port> depends on the port configuration of the EBICS Server. Do not change the ebics/EbicsServlet part of this URL. |
| Import PKCS12 file | Do not select this option. |
| Protocol versions |
Select the EBICS standard version you intend to use for exchanges between the bank and remote client.
|
| Signature versions |
Select the EBICS public key signature versions you intend to use for exchanges between the bank and remote clients.
|
| Force certificates |
Select this option to require the customer to use X.509 certificates. |
EBICS Server creates a new bank object.
EBICS Server creates an entity in PassPort with the following parameters:
EBICS Server generates the following RSA public keys and their corresponding private key in PassPort:
The PassPort entity is trusted, therefore the created certificates are trusted. This means that the certificates are used as a Trust Anchor.
EBICS security services via PassPort