You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/user-guide/setup/ssl-setup.md
+14-8
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ order: 20
6
6
7
7
## Overview
8
8
9
-
In general, Git servers require secure connections. Therefore, abapGit is using secure connections based on HTTPS to access Git servers.
9
+
In general, Git servers require secure connections. Therefore, abapGit uses secure HTTPS connections to access Git servers.
10
10
11
-
Note: Using unsecure HTTP connections is possible but strongly discouraged since the content of your repository would become visible on the network.
11
+
Note: Using unsecured HTTP connections is possible, but it is strongly discouraged since the content of your repository will become visible on the network.
12
12
13
13
To support HTTPS, your SAP system must be configured accordingly:
14
14
@@ -26,7 +26,7 @@ We use GitHub.com as an example for configuring secure connections. This is also
26
26
27
27
### SAP Crypto Library
28
28
29
-
Secure connections require installation of the SAP Crypto Library (CommonCryptoLib 8). Since SAP NetWeaver 7.4 this library is installed with the system. However, if your system is older or not up-to-date, you might have to update the library to a more recent version.
29
+
Secure connections require the installation of the SAP Crypto Library (CommonCryptoLib 8). Since SAP NetWeaver 7.4 this library is installed with the system. However, if your system is older or not up-to-date, you might have to update the library to a more recent version.
30
30
31
31
:::note
32
32
It's highly recommended to run a recent version of the Crypto Library to avoid known security issues. As of December 2022, the latest version is `8.5.47`.
@@ -70,7 +70,7 @@ If configured correctly, transaction `SMICM` > Goto > Services (`Shift + F1`) wi
70
70
71
71
As a default, abapGit uses an anonymous client connection (`ANONYM - SSL Client (Anonymous)`). A secure connection requires that the Git server certificate is available in the certificate list. The certificate must also be valid!
72
72
73
-
First, download the server certificates to you local machine. Then import and add these certificates to your SAP system.
73
+
First, download the server certificates to your local machine. Then import and add these certificates to your SAP system.
74
74
75
75
[Trust Manager in SAP Documentation](https://help.sap.com/docs/SAP_NETWEAVER_750/280f016edb8049e998237fcbd80558e7/4c5bdb17f85640f1e10000000a42189c.html)
76
76
@@ -94,7 +94,7 @@ If done correctly, transaction `STRUST` will show the Git server certificates in
94
94
95
95
1. Use Firefox to go to [https://github.com](https://github.com)
96
96
2. Click on the lock icon and then "More Information ..." and there "View Certificate"
97
-
3. Switch to the Details Tab and choose the first certificate of the hierarchy and click Export
97
+
3. Switch to the Details Tab, choose the first certificate of the hierarchy and click Export
98
98
4. Do the same for the next certificate in the hierarchy
99
99
100
100
##### Option C - Safari
@@ -108,13 +108,13 @@ If done correctly, transaction `STRUST` will show the Git server certificates in
108
108
##### Option D - Manual
109
109
110
110
1. Goto GitHub, find the certificate that it is using
111
-
2. Download certificate from [https://www.digicert.com/digicert-root-certificates.htm](https://www.digicert.com/digicert-root-certificates.htm)
111
+
2. Download the certificate from [https://www.digicert.com/digicert-root-certificates.htm](https://www.digicert.com/digicert-root-certificates.htm)
112
112
113
113
#### Install the Certificate Files
114
114
115
115
1. Install the certificates in transaction `STRUST`:
116
116
2. Click on the Change button
117
-
3. Open "SSL client Client SSL Client (Anonymous)" folder
117
+
3. Open the "SSL client Client SSL Client (Anonymous)" folder
118
118
4. In the third box called "Certificate", click on the bottom-left button "Import certificate" to bring the certificate into the system
119
119
5. Select "Add to certificate list"
120
120
6. Repeat the process for all downloaded certificates
@@ -132,6 +132,12 @@ Report [ZABAPGIT_TEST_SSL](/user-guide/setup/ssl-test.md) can be used to verify
132
132
133
133
### Troubleshooting
134
134
135
+
:::info
136
+
The following SAP Notes contain the details for setup and troubleshooting:
137
+
- SAP Note [510007](https://me.sap.com/notes/510007) - Additional considerations about setting up SSL on Application Server ABAP
138
+
- SAP Note [2368112](https://me.sap.com/notes/2368112) - Outgoing HTTPS connection does not work in AS ABAP
139
+
:::
140
+
135
141
Connection issues typically lead to "Access to resource forbidden" (HTTP 403) or "Misdirected Request" (HTTP 421) errors.
136
142
137
143
1. Go to transaction `SMICM`
@@ -140,7 +146,7 @@ Connection issues typically lead to "Access to resource forbidden" (HTTP 403) or
140
146
4. Select Goto > Trace Files > Display All to view the ICM trace (`dev_icm`)
141
147
142
148
- Check for any errors
143
-
- Find the section called "SSL Initialization" and check if it ends with "Success - SapCryptoLib SSL ready!"
149
+
- Find the "SSL Initialization" section and check if it ends with "Success - SapCryptoLib SSL ready!"
144
150
- Compare the listed SSL settings to the recommended settings of SAP Note 51007 (and mentioned above)
0 commit comments