Академический Документы
Профессиональный Документы
Культура Документы
- How To Guide -
SEEBURGER AG
Platform: PI
Release: 7.1x/7.3x
SEEBURGER AG
Inhalt
AS2 CERTIFICATE HANDLING
Importing certificates
Exporting a certificate
CONFIGURATION ERRORS
11
General
11
11
11
12
12
13
14
14
16
16
16
17
17
18
19
19
APPENDIX
21
Further Information
21
Seite 2/21
19.03.2013
SEEBURGER AG
Icons
Symbol
Description
Caution
Warning
Note
Recommendation
Requirements
Information
Example
Code
Seite 3/21
19.03.2013
SEEBURGER AG
Fill in View Name and Description for the new view. Click Create.
19.03.2013
SEEBURGER AG
Importing certificates
To be able to verify signed messages from trading partners their certificates have to be imported in the
new Keystore View.
To import a certificate from a trading partner click the Import Entry button in the Key Store View
Details pane.
Choose X.509 Certificate, select the certificate file from the file system and click Import.
Note:
The name of the imported certificate can be changed using the Rename button.
Fill in an Entry Name and check Store Certificate to create a certificate (otherwise only a private key
will be created). Click Next.
Seite 5/21
19.03.2013
SEEBURGER AG
Fill in the Subject Properties. If required, properties can be added or removed by clicking the Add or
Remove button. Skip Step 3 and 4 by clicking the Finish button.
Seite 6/21
19.03.2013
SEEBURGER AG
Exporting a certificate
Export own certificates to provide them to trading partners by selecting the certificate which shall be
exported and clicking the Export Entry button.
Select the preferred export format and click the Download link.
Seite 7/21
19.03.2013
SEEBURGER AG
Seite 8/21
19.03.2013
SEEBURGER AG
Select the user seeas2 and switch to the Assigned Roles tab in the Details of User pane. Click
Modify.
Search for the Role view-creator*. Select the role of the Keystore view and Add it to the user. Save
the changes.
Seite 9/21
19.03.2013
SEEBURGER AG
Seite 10/21
19.03.2013
SEEBURGER AG
Configuration Errors
General
Note:
The following errors were provoked by an AS2 adapter but can be devolved to every other
SEEBURGER adapter using encryption and signing.
Solution:
Check your Receiver Agreement
Seite 11/21
19.03.2013
SEEBURGER AG
Solution:
Check the adapter user in the Identity Management of the Netweaver Administrator (NWA). There has
to be an assigned role to the Keystore view which contains the certificates and private keys.
No signature certificate
Error:
Solution:
Check your Receiver Agreement
Seite 12/21
19.03.2013
SEEBURGER AG
Solution:
Check if a Report channel and the corresponding Sender Agreement are configured.
Seite 13/21
19.03.2013
SEEBURGER AG
Solution:
Solution:
Check your SSL configuration in the communication channel
Seite 14/21
19.03.2013
SEEBURGER AG
Caution:
If a SSL certificate is newly imported a restart of the J2EE Engine is required in order that the
changes take effect.
Seite 15/21
19.03.2013
SEEBURGER AG
Solution:
Check the Decryption Key in your Sender Agreement.
Decryption failed
Error:
Solution:
Check the Decryption Key in your Sender Agreement.
Seite 16/21
19.03.2013
SEEBURGER AG
Authentication error
Error:
Solution:
Check the Authentication Certificate in your Sender Agreement.
Seite 17/21
19.03.2013
SEEBURGER AG
Caution:
If not OK, apply SAP Note 1287778.
Seite 18/21
19.03.2013
SEEBURGER AG
Check if the Unlimited Strength Policy files are installed on all server nodes.
Caution:
If not OK, see SeeMasterInstallationGuide.pdf chapter 4 Note on Cryptography and
SAP Note 989517.
Solution:
Check the Signing Key in your Sender Agreement.
Solution:
Check the Authentication Certificate in your Sender Agreement for the Report channel.
Seite 19/21
19.03.2013
SEEBURGER AG
Seite 20/21
19.03.2013
SEEBURGER AG
Appendix
Further Information
Information:
For further information refer to the SEEBURGER Master Configuration Guide and the Adapter
manuals coming with the solution release.
Seite 21/21
19.03.2013