Skip to content

W-22454128 IP Allowlisting for Connected Apps #144

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
valkyrie69 wants to merge 2 commits into
base: latest
Choose a base branch
from
Open

W-22454128 IP Allowlisting for Connected Apps #144

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d50aa87
W-22454128 IP Allowlisting for Connected Apps
valkyrie69 May 14, 2026
51687f6
W-22454128 IP Allowlisting Connected Apps Note
valkyrie69 May 14, 2026
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
11 changes: 9 additions & 2 deletions modules/ROOT/pages/osv2-connected-apps.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,18 @@
= Configuring Connected Apps
= Configuring Connected Apps for Object Store

The Connected Apps feature enables you to integrate external applications with Anypoint Platform by providing access to those applications without sharing your user credentials.
Connected apps provide secure, credential-free access to Object Store for external applications and Mule integrations. After creating a connected app in Access Management, use the generated client ID and secret to authenticate with the Object Store v2 API.

For information about Connected Apps, see
xref:access-management::connected-apps-overview.adoc[] and
xref:access-management::connected-apps-developers.adoc[].

[IMPORTANT]
====
If your organization has IP allowlisting enabled for connected apps, you must either allowlist the outbound IPs of the runtime where your Mule app is deployed, or exempt the connected app from IP enforcement. Without one of these steps, token generation fails and your Mule flows stop processing messages.

If your app runs on CloudHub without static IPs or on CloudHub 2.0 Shared Space, you must exempt the connected app. These deployment models use dynamic or shared IPs that can't be reliably allowlisted. For guidance on all deployment models and exemption steps, see xref:access-management::managing-ip-allowlists.adoc#configure-ip-allowlisting-connected-apps[Configure IP Allowlisting for Connected Apps].
====


[[configure-os-conn-app]]
== Configure a Connected App in Access Management
Expand Down