Getting started Community Training Tutorials Documentation APIs, AI & Tools
Troubleshoot Access Management
These tips provide information on what to do if you encounter issues.
Problems with Accessing Anypoint Platform
Signin Credentials are Not Recognized
If your credentials aren’t recognized when you sign in to Anypoint Platform, try the following:
-
Check that you are using the correct URL to sign in to your organization.
If your organization uses an external identity management system, your signin URL is anypoint.mulesoft.com/accounts/login/yourOrganizationDomain.
-
Verify that you are using the correct username and password for the account.
-
If your organization isn’t using an external identity management system and your signin credentials aren’t working, reset your password or ask your Organization Administrator if your account is still active.
Access Management Invitation Link Returns an Error
If you click the link in your invitation and an error is returned, your invitation may have expired or been rescinded. Please contact your Organization Administrator for a new invitation. If your organization has no other active users who can resend the invitation, see Invitation, Welcome, and License Key Emails.
Administrative Access Lost
To avoid losing administrator access, assign the Organization Administrator permission to more than one user.
If you do lose administrator access, for example, if all Anypoint Platform administrators have left the company, are unknown, or have deactivated or deleted accounts, you must contact MuleSoft Support to regain access.
-
Log in to the MuleSoft Support Portal and request the organization reclamation process.
-
You must provide:
-
A signed letter on company letterhead from a C-level executive that requests the administrator change.
-
Your company details, such as your company name and Anypoint Platform organization name or ID.
-
Information about the previous administrators, such as their names and email addresses.
-
The name and email address of the new administrator.
-
OpenID Connect Client Management
Error received when you try to update a client application
If you receive an There was an error while talking to CoreServices when you try to update a client application under OpenID Connect management, this is because updates of clients created through this integration are not currently supported.
Error Received When Doing a Redirect
When a redirect to the OpenID Connect Provider occurs, you receive an Invalid Scopes error.
Cause: This can happen if the openid, profile, and email scopes aren’t supported by the auto-registered client.
Solution: Add the openid, profile, and email scopes to the client manually.



