...
<servers>
<server>
<id>MuleRepository</id>
<username>mule.username</username>
<password>mule.password</password>
</server>
</servers>
...
<profiles>
<profile>
<id>Mule</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>MuleRepository</id>
<name>MuleRepository</name>
<url>https://repository.mulesoft.org/nexus-ee/content/repositories/releases-ee/</url>
...
</repository>
</repositories>
</profile>
</profiles>
To Build a Mule OAuth 2 Provider
To build a provider from MuleSoft Consulting on Mule Runtime 3.8.x, perform this task.
-
Set up credentials in the Mule EE Repository by creating, or by adding the credentials to, the Maven
settings.xml
file. This file is typically located in~/.m2/settings.xml
on Linux or Mac OSX: -
Download the OAuthProviderStudioArchive using the link at the bottom of this topic.
-
Launch Studio, and choose File > Import.
-
In Select, expand Anypoint Studio and choose Anypoint Studio Generated Deployable Archive.
-
Browse to the
OAuthProviderStudioArchive.zip
you downloaded, and click Finish. -
Log into your Anypoint platform account.
-
Access the client ID and client secret of the account you are using to create the provider application.
-
Enter your client Id and client Secret in Anypoint Studio > Preferences > Anypoint Studio > Anypoint Platform for APIs.
This step is necessary to test the local provider.
-
In Project Explorer, right-click the project name and select Run As > Mule Application with Maven.
-
In Configure Maven, enter your Maven installation home directory, and click Test Maven Configuration.
Assuming the test was successful, click OK; otherwise, troubleshoot the Maven problem. The console reports that the app deployed. Next, test the local provider.