You can configure permission types to enable a user to access the EBICS Client dashboard interface.
You can configure the following permission types to enable a user to access the EBICS Client dashboard interface:
An EBICS Client admin can configure an existingSterling B2B Integratoruser as an EBICS Client user or EBICS Client operator. The admin can also configure the following entities in EBICS Client dashboard interface:
- Bank profile
- User profile
- Offer
- File format
- Keys
- User permission
- View events
- Search for orders
However, an EBICS Client admin user cannot submit orders.
Technical User
EBICS Client also supports a technical user. A technical user is an EBICS Client user configured to submit orders on behalf of a non-technical (human user) EBICS Client user using a back-end system. The technical user is associated with a non-technical user. TheSystemIDfield in the EBICS request is populated with the technical subscriber user ID. Electronic signature (ES), authorization and encryption certificates are linked to the system ID and are verified accordingly. If a payload is received over a file system adapter, or any other technical adapter, such as, JSM or FTP, then EBICS Client application uses the ID of the technical user specified in the XML file and submits the order. If the payload is received over an EBICS Client user’s mail box, then the user ID of the user is used to submit the order. Permissions for order submission are inherited from the user ID when an order is submitted over a user’s mailbox. For example, if an upload order type with file format pain.xxx.cfonb160 is being submitted, EBICS Client verifies the permissions of the user to submit the order type file format combination. However, EBICS Client verifies the certificates for electronic signature, authentication, and encryption specified for the system ID. The electronic signature for a technical user is set to Transport signature of type T.
A compressed file (.zip) containing an XML file, ordermetadata.xml, and optionally the payload (for FUL and similar order types) are uploaded to the EBICS Client from the back-end. If the file name of the payload has non-ASCII characters, then use the jar utility that comes with the Java Development Kit (JDK) installed withSterling B2B Integratorto create a compressed file. You have to execute the jar utility from the command prompt in Windows or the terminal in UNIX with the following parameters: jar cFM <zip_fileName> ordermetadata.xml < payload_fileName with non-ASCII characters> . If the file name of the payload has only ASCII characters, then either the jar utility or any application such as WinZip or WinRAR can be used to create a compressed file.
EBICS Client collects the compressed file through an adapter such as the File System Adapter (FSA) configured onSterling B2B Integrator. After the compressed file is received, the EBClientOrderPreProcess business process extracts the contents of the XML file and generates an EBICS request based on the values specified in the XML file. The XML file must conform to the following XSD. The technical user is specified in the System ID field.
<?xml version="1.0" encoding="UTF-8"?><xsd:schema xmlns:xsd= "http://www.w3.org/2001/XMLSchema"> <xsd:element name="PartnerID" type="xsd:string"/> <xsd:element name="UserID" type="xsd:string"/> <xsd:element name="OrderType" type="xsd:string"/> <xsd:element name="SystemID" type="xsd:string"/> <xsd:element name="Parameter"> <xsd:complexType> <xsd:sequence> <xsd:element ref="Name" minOccurs="1" maxOccurs="1"/> <xsd:element ref="Value" minOccurs="1" maxOccurs="1"/> <xsd:element ref="Type" minOccurs="0" maxOccurs="1"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="ParameterList"> <xsd:complexType> <xsd:sequence> <xsd:element ref="Parameter" minOccurs="0" maxOccurs="unbounded"/> </xsd:sequence> </xsd:complexType> </xsd:element> <xsd:element name="UserAuthNewPubKeyID" type="xsd:string"/> <xsd:element name="UserAuthNewPriKeyAlias" type="xsd:string"/> <xsd:element name="PAYLOADMSGID" type="xsd:string"/> <xsd:element name="Product" type="xsd:string"/> <xsd:element name="Value" type="xsd:string"/> <xsd:element name="UserEncrNewPubKeyAlias" type="xsd:string"/> <xsd:element name="UserNewSignatureVersion" type="xsd:string"/> <xsd:element name="UserSignNewPubKeyID" type="xsd:string"/> <xsd:element name="Type" type="xsd:string"/> <xsd:element name="UserEncrNewPubKeyID" type="xsd:string"/> <xsd:element name="UserNewAuthVersion" type="xsd:string"/> <xsd:element name="PreValidation" type="xsd:string"/> <xsd:element name="UserAuthNewPriKeyID" type="xsd:string"/> <xsd:element name="UserSignNewPriKeyAlias" type="xsd:string"/> <xsd:element name="UserAuthNewPubKeyAlias" type="xsd:string"/> <xsd:element name="HostID" type="xsd:string"/> <xsd:element name="autoSubmit" type="xsd:string"/> <xsd:element name="Name" type="xsd:string"/> <xsd:element name="UserSignNewPriKeyID" type="xsd:string"/> <xsd:element name="UserEncrNewPriKeyID" type="xsd:string"/> <xsd:element name="UserNewEncVersion" type="xsd:string"/> <xsd:element name="FileFormat" type="xsd:string"/> <xsd:element name="DownloadDateRangeEnd" type="xsd:string"/> <xsd:element name="SecurityMedium" type="xsd:string"/> <xsd:element name="UserSignNewPubKeyAlias" type="xsd:string"/> <xsd:element name="UserEncrNewPriKeyAlias" type="xsd:string"/> <xsd:element name="orderIdPrefix" type="xsd:string"/> <xsd:element name="DownloadDateRangeStart" type="xsd:string"/> <xsd:element name="orderMetaData"> <xsd:complexType> <xsd:all> <xsd:element ref="HostID" minOccurs="1" maxOccurs="1"/> <xsd:element ref="PartnerID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="PAYLOADMSGID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="PreValidation" minOccurs="0" maxOccurs="1"/> <xsd:element ref="Product" minOccurs="0" maxOccurs="1"/> <xsd:element ref="orderIdPrefix" minOccurs="0" maxOccurs="1"/> <xsd:element ref="SecurityMedium" minOccurs="0" maxOccurs="1"/> <xsd:element ref="OrderType" minOccurs="0" maxOccurs="1"/> <xsd:element ref="SystemID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="FileFormat" minOccurs="0" maxOccurs="1"/> <xsd:element ref="autoSubmit" minOccurs="0" maxOccurs="1"/> <xsd:element ref="DownloadDateRangeStart" minOccurs="0" maxOccurs="1"/> <xsd:element ref="DownloadDateRangeEnd" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserSignNewPubKeyAlias" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserSignNewPubKeyID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserSignNewPriKeyAlias" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserSignNewPriKeyID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserAuthNewPubKeyAlias" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserAuthNewPubKeyID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserAuthNewPriKeyAlias" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserAuthNewPriKeyID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserEncrNewPubKeyAlias" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserEncrNewPubKeyID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserEncrNewPriKeyAlias" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserEncrNewPriKeyID" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserNewSignatureVersion" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserNewAuthVersion" minOccurs="0" maxOccurs="1"/> <xsd:element ref="UserNewEncVersion" minOccurs="0" maxOccurs="1"/> <xsd:element ref="ParameterList" minOccurs="0" maxOccurs="1"/> </xsd:all> </xsd:complexType> </xsd:element> </xsd:schema> Parent Topic
Sterling B2B Integrator - EBICS Client Architecture and Key Features
Next Topic
Sterling B2B Integrator - Managing certificates and keys for users