Skip to content

Commit

Permalink
Update from SAP DITA CMS (squashed):
Browse files Browse the repository at this point in the history 
commit 8edfc9f525e4983b7bf5bd9c7a1d0d620e11601f
Author: REDACTED
Date:   Thu Feb 8 18:27:41 2024 +0000

    Update from SAP DITA CMS 2024-02-08 18:27:41
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Language: en-US

commit 1d9ccf5992473b9eebb333625d9ed616614ec585
Author: REDACTED
Date:   Thu Feb 8 18:15:34 2024 +0000

    Update from SAP DITA CMS 2024-02-08 18:15:34
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Language: en-US

commit 23f148a926611de3d74d976af8dfaedf94864dbb
Author: REDACTED
Date:   Thu Feb 8 14:51:49 2024 +0000

    Update from SAP DITA CMS 2024-02-08 14:51:49
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Language: en-US

commit 1ee7ef3c87fc0674a5099933b0a77d98c5190711
Author: REDACTED
Date:   Thu Feb 8 12:19:13 2024 +0000

    Update from SAP DITA CMS 2024-02-08 12:19:13

##################################################
[Remaining squash message was removed before commit...]
  • Loading branch information
@ditaccms-bot
ditaccms-bot committed Feb 9, 2024
1 parent 779defb commit 76ddfb9
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 10 deletions.
4 changes: 3 additions & 1 deletion docs/1-connectivity-documentation/configure-trust-13bfb28.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,9 @@ To enable secured backend communication, you must add trusted certificate author
> You must provide the CA's X.509 certificates in `DER` or `PEM` format.
> ### Caution:
> If you don't want to specify explicit CAs you are going to trust, but rather **trust all backends**, you can switch off the handle. In this case, the allowlist is ignored. This option considered less secure, since all backends are trusted now.
> If you don't want to specify explicit CAs for trust, but rather **trust all certificates used by your backends**, you can switch off the trust store. In this case, the allowlist is ignored. However, this is considered less secure, since all server certificates are trusted and the issuing CA is not checked.
>
> As a result, certain attacks on the hop between Cloud Connector and internal systems can be performed more easily. Therefore, **we strongly recommend that you *don't do this in productive installations***.
>
> ![](images/SCC_Configure_Trust_-_Trust_Store_TrustAll_bb6c361.png)
Expand Down
18 changes: 9 additions & 9 deletions docs/1-connectivity-documentation/prerequisites-e23f776.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -749,7 +749,7 @@ Europe \(Frankfurt\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -861,7 +861,7 @@ Europe \(Frankfurt\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -1025,7 +1025,7 @@ US East \(VA\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -1250,7 +1250,7 @@ Brazil \(São Paulo\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -1314,7 +1314,7 @@ Japan \(Tokyo\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -1421,7 +1421,7 @@ Australia \(Sydney\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -1485,7 +1485,7 @@ Asia Pacific \(Singapore\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -1549,7 +1549,7 @@ Asia Pacific \(Seoul\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down Expand Up @@ -1701,7 +1701,7 @@ Canada \(Montreal\) - AWS
>
> **Action:**
>
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration accordingly. The new IP addresses may be used starting from end of Q1, 2024.
> If you restrict system access by *allowlisting IPs* in firewall rules, make sure you update your configuration as soon as possible. The new IP addresses may be used starting from end of Q1, 2024.


Expand Down

0 comments on commit 76ddfb9

Please sign in to comment.