Skip to content

W-22513829-authorization-error-eme-dm #473

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dmerlob wants to merge 1 commit into
base: latest
Choose a base branch
from
Open

W-22513829-authorization-error-eme-dm #473

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions modules/ROOT/pages/connected-apps-org-admin.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,23 +13,23 @@ Connected app ownership gets transferred to the root organization owner when the

To maintain security, manually rotate the client secrets of all connected apps in the organization after the transfer. For more information about how to manually rotate client secrets, see <<modify-client-secret>>.

You can also reset client secrets programmatically using the https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/access-management-api/minor/1.0/console/method/%236918/[Access Management API].
You can also reset client secrets programmatically using the https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/access-management-api/minor/1.0/console/method/%236918/[Access Management API].

== Manage Owned Apps

To maintain security, you can view and manage connected apps only if you have the Organization Administrator permission in the root organization or in the business group where the connected app resides.

To manage your connected apps:

. Navigate to *Access Management* and select the *Connected Apps* tab.
. Add and edit apps in the *Owned Apps* section.
. Navigate to *Access Management* and select the *Connected Apps* tab.
. Add and edit apps in the *Owned Apps* section.
. Manage app access in the *Authorizations* section.

=== Edit the App Owner

Organization administrators can edit the owner of the connected app and transfer the ownership to other administrators:

. In *Access Management* > *Connected Apps* > *Owned Apps*, click the app name.
. In *Access Management* > *Connected Apps* > *Owned Apps*, click the app name.
. Make the changes and click *Save changes*.

[[modify-client-secret]]
Expand All @@ -54,14 +54,15 @@ image::connected-apps-edit-mode.png[Edit mode for a connected app]
. In the *Authorizations* tab, select the app.
. Click the more actions menu (*...*) for the application and select *Show details*.

=== Revoke Authorization
=== Revoke Authorization

When you revoke an app’s access, the app’s OAuth 2.0 access tokens and refresh tokens are revoked, and the app can no longer access user data. This action can't be undone.

. In the *Authorizations* tab, select the app.
. Click the more actions menu (*...*) for the selected application and select *Remove*.
. Click *Remove*.
. Click *Remove*.

[[configure-authorization-policies]]
== Configure Authorization Policies

You can configure one of these types of authorization policies for your users:
Expand Down