Skip to content
Sample Connectors for VMware Workspace ONE Mobile Flows
Branch: master
Clone or download
rworsnop Merge pull request #22 in UFO/open-source-connectors from bugfix/APF-…
…1963-aw-connector-actions-are-failing to master

* commit '4a6a668b96ccfc97d9cf40a434bf66d5b31355bd':
  APF-1963 Fix app install action.
Latest commit c6223d9 Feb 5, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.mvn/wrapper APF-554 Add connector files Nov 8, 2017
connectors Merge pull request #22 in UFO/open-source-connectors from bugfix/APF-… Feb 5, 2019
.travis.yml Create .travis.yml Jan 3, 2018 Update contributing stuff Dec 15, 2017
NOTICE.txt APF-1042: PR feedback Apr 19, 2018
Vagrantfile Add Mar 1, 2018

Workspace One Connectors


These are connectors that have been developed for Workspace One Mobile Flows. Although all of them can be used as-is, they can also be used as base from which VMware customers can develop their own connectors.

The connectors are written in Java and use the Spring Framework. More specifically, they use Spring Boot, embedding Tomcat 8.5.

For a detailed, language-neutral, specification for how to develop connectors, please see the Card Connectors Guide.

This repository also includes common libraries. Please see their README for more details.


The connectors can be run as Docker containers.


  • Docker


The latest published versions of the connectors are available in the Docker Hub registry.

For example, you can run the latest jira-connector with:

docker run --name jira-connector \
           -p 8080:8080 \
           -d \
           ws1connectors/jira-connector \
           --server.port=8080 \


The connectors can be built, installed, and run as RPMs.


Vagrant isn't necessary if you're using an RPM-based OS, such as CentOS or RHEL. You will need the following packages though:

yum install -y git rpm-build vim nmap-ncat java-1.8.0-openjdk-devel


Clone this repository or download as zip. Unzip the repo if you downloaded a zip. Use the below command from within the repository directory to build the RPMs:

./mvnw clean install -Pmake-rpm


Each connector has its own RPM. For example, jira-connector-1.0.0.noarch.rpm. This can be found at connectors/jira/target/rpm/jira-connector/RPMS/noarch/.

Java 11 is a prerequisite. Installation instructions can be found here.

Once the JDK is downloaded and unpacked, a soft link should be created. For example:

ln -s /usr/lib/jvm/jdk-11.0.1/bin/java /usr/bin/java

The next step is to use the RPM to install the connector as a service. For example:

yum install jira-connector-1.0.0.noarch.rpm

Before the service can be run, some configuration is required. The connectors authenticate requests expecting an access token from VMware IDM. These tokens are JWTs whose signatures must be verified using a public key. This public key is acquired from a URL that is supplied to the connector via a new configuration file.

For example, for the Jira connector:

echo "security.oauth2.resource.jwt.key-uri=" \
> /etc/opt/vmware/connectors/jira/

The hostname of the URL will vary depending on your IDM tenant.

The configuration file created above must be part of the roswell user and group. Again, using Jira as an example:

chown roswell:roswell /etc/opt/vmware/connectors/jira/

The connector being a Spring Boot application, many other configuration options are available—for example, server.port. Please see the Spring Boot documentation for more details.

There might also be connector-specific configuration required. Please see the README files within the individual connectors for further details.

Once the connector is configured, it can be started. For example:

systemctl start jira-connector

Check the status after about 10-20 seconds to make sure the service is good:

systemctl status jira-connector

Also check the logs if there are problems:

less /var/log/vmware/connectors/jira/connector.log


The connector can be updated using yum. For example, to update the Jira connector from 1.0.0 to 1.0.1:

yum upgrade jira-connector-1.0.1.noarch.rpm

Updating will not touch your overriding in /etc. It is probably a good idea to take a glance at /opt/vmware/connectors/jira/ after updating to verify that there aren't any new things in the config that you should override. If there are any new settings you wish to configure, make sure you do so in the in /etc so that future updates/uninstalls don't throw away your config.


yum remove jira-connector

Fat Jars

The connectors can also be built and run as executable "fat" jars.



Clone this repository or download as zip. Unzip the repo if you downloaded a zip. Use the below command from within the repository directory to build the fat JARs:

./mvnw clean install


After building the JAR(s), you can run them with java -jar. For example, here is a command to run the jira-connector:

java -server \
     -jar \
     connectors/jira/target/jira-connector-2.1-SNAPSHOT.jar \
     --server.port=8080 \


For more information on common mistakes, see


The connectors-workspace-one project team welcomes contributions from the community. Before you start working with connectors-workspace-one, please read our Developer Certificate of Origin. All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch. For more detailed information, refer to


Workspace One Connectors are available under the BSD 2 license

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.