Skip to content

Commit

Permalink
Update from SAP DITA CMS (squashed):
Browse files Browse the repository at this point in the history
commit aaba3cafaab46babc29bdef55f51c6edb1550006
Author: REDACTED
Date:   Wed Nov 13 11:43:11 2024 +0000

    Update from SAP DITA CMS 2024-11-13 11:43:11

    Project: dita-all/wbz1500991557538
    Project map: 1334e860f4d64684a929f6a7afeea339.ditamap
    Output: loio629f7cb06f6947988dcaf8bedbe45873
    Language: en-US
    Builddable map: 542fb1b8806149fc8f6953d896e46f50.ditamap

commit 1be0a72ab12ed9a86779a047c4031e87b640dd53
Author: REDACTED
Date:   Wed Nov 13 11:21:49 2024 +0000

    Update from SAP DITA CMS 2024-11-13 11:21:49

    Project: dita-all/wbz1500991557538
    Project map: 1334e860f4d64684a929f6a7afeea339.ditamap
    Output: loio629f7cb06f6947988dcaf8bedbe45873
    Language: en-US
    Builddable map: 542fb1b8806149fc8f6953d896e46f50.ditamap

commit 34754eeccd575e7806942bfda8ca9d9074ff4884
Author: REDACTED
Date:   Wed Nov 13 08:25:56 2024 +0000

    Update from SAP DITA CMS 2024-11-13 08:25:56

    Project: dita-all/wbz1500991557538
    Project map: 1334e860f4d64684a929f6a7afeea339.ditamap

##################################################
[Remaining squash message was removed before commit...]
  • Loading branch information
ditaccms-bot committed Nov 13, 2024
1 parent 615222c commit 675b28a
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 55 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The authorization data for a reuse service is shared among multiple business app

## Context

A reuse service is consumed by multiple business applications, for example application 1 and application 2. The authorization data is not separated among the applications, though. The applications, which are in the same SAP Cloud Identity Services tenant, share the authorization policies and assignments of the reuse service. Thus you make sure that the authorization policies of the reuse service are consistent across different applications.
A reuse service is consumed by multiple business applications, for example application 1 and application 2. All applications and reuse services can have their own set of authorization policies that are always tied to the application or to the reuse service. For easy maintenance, it is possible to manage the authorization policies of the reuse service in the *Authorization Policies* tab of the application that consumes the reuse services.

When an administrator assigns a user to an authorization policy of the reuse service, the reuse grants this permission regardless of the authorization context of the business application. That means, if the user logs on to application 1 or application 2, the permissions for the reuse service are the same, meaning the authorization policies of the reuse service.

Expand Down
54 changes: 0 additions & 54 deletions docs/tenants-93160eb.md
Original file line number Diff line number Diff line change
Expand Up @@ -488,60 +488,6 @@ SAP
<tr>
<td valign="top">

Google Cloud

</td>
<td valign="top">

KSA \(Dammam\)

</td>
<td valign="top">

sa30

</td>
<td valign="top">

Dammam, Saudi Arabia, Middle East

</td>
<td valign="top">

Google Cloud

</td>
</tr>
<tr>
<td valign="top">

Google Cloud

</td>
<td valign="top">

KSA \(Dammam\)

</td>
<td valign="top">

sa30

</td>
<td valign="top">

Saudi Arabia \(Riyadh, Dammam\)

</td>
<td valign="top">

SAP, Google Cloud

</td>
</tr>
<tr>
<td valign="top">

Amazon Web Services

</td>
Expand Down

0 comments on commit 675b28a

Please sign in to comment.