Have a question? Want to report an issue? Contact JFrog support

Skip to end of metadata
Go to start of metadata

Overview

To get you up and running as quickly and easily as possible for a new installation, Mission Control provides an onboarding wizard. The onboarding wizard is invoked first time you start up Mission Control. It will take you through the steps of initial configuration using a convenient and intuitive UI. 

From Mission Control version 3.0 and above,  Mission Control uses an external Artifactory service for managing Mission Control authentication and authorizations settings and serves as an authentication provider. This leading Artifactory service manages Mission Control users, groups, and permissions. The Authentication Provider is configured in the Mission Control Onboarding Wizard and is mandatory. For more information, see Authentication Provider.

Page contents

 

Requirement

  • Make sure you install all your services prior to running Mission Control.
  • If you are using license buckets, you need to ensure the host running Mission Control can to connect to URLs prefixed with https://dl.bintray.com/. For details, please refer to Adding a License Bucket

Getting Started with Enterprise+

Before installing your Enterprise+, we strongly recommend that you read the Getting Started with Enterprise+ which gives the full workflow for installing the complete JFrog Enterprise+ offering and shows how all of its services work together to provide an end-to-end solution for fast release and distribution of binary artifacts.


Mission Control Onboarding Wizard

The onboarding wizard makes sure you get Mission Control set up with the minimal information needed to get started. 

 




Step 1: Welcome

Starting Mission Control for the first time launches the Mission Control onboarding wizard. Click Next to get started.

Step 2: Set Admin Password

Mission Control creates a default user with admin privileges predefined in the system. In this step, you can change the password or skip and change it at a later stage. If you choose to skip the default password will remain.

Step 3: Basic Configuration

Configure the Mission Control base URL through which Mission Control can be accessed. The Site list displays the default site, MC_Site that is automatically created. For new installations, there will only be a single site in the Site list. For upgrades, there may multiple sites and the user can choose to change the default site.

This step is mandatory.

You can proceed to set the HTTP proxy to allow Mission Control access to external services. This parameter is optional.



Step 4: Add License Buckets:

License Buckets allow you to easily manage your Artifactory service licenses.

To obtain your bucket of licenses, please contact your JFrog representative who will create a bucket with the number of licenses you require and send them to you.

Please note that you will receive two email messages from: service@jfrog.com with a signed URL and license key. For more information, see License Bucket Management.

For Enterprise+ Customers:

Enterprise+ users can add two buckets for Enterprise+ and (Artifactory) Edge. 

In this step, add the Enterprise+ bucket and then proceed to add the Edge bucket. 


Step 5: Authentication Provider:

Assign an Artifactory service as the Authentication Provider that is responsible for managing Mission Control authentication and authorization.

This step is mandatory.

You can perform one of the following:

  • Select an existing Artifactory service: If you are upgrading Mission Control, a list of existing Artifactory services are displayed. Select the Artifactory service that functions as the Authentication Provider.
  • Add a new Artifactory service: If you are installing from scratch, set the service details (name, URL, site, and credentials) and assign a license bucket.




Step 6: Summary

Displays the settings configured according to your selection. Click Finish to start using Mission Control.

If you have selected the Enterprise+ buckets, you will view the following summary page:


Accessing Mission Control Using Single Sign-On (SSO)

When you log in to Mission Control, the following screen opens. Use your Authentication Provider Artifactory login credentials to log in to Mission Control. Contact your admin if you do not know your credentials.


Generating Tokens for API calls

Overview

Prior to running Mission Control REST API calls you need to generate an access token. The token is valid for 60 minutes. 



Hardening Security for Secrets 

From Mission Control 3.4, you can configure encrypted parameters such as secrets to connect to external resources such as passwords. While these secrets can be stored in the Mission Control properties file, we highly recommend against it as it poses a risk of being exposed.

To keep your secrets safe, preload the secrets from the properties file allowing them to be encrypted and written back to Properties file when first read. 

The snippet below shows the list of properties that are encrypted when first read.

#Mission control admin password
users.admin.password
#Mongo DB password (will be deprecated)
spring.data.mongodb.password
#PostgreSQL Password for jfmc server
spring.datasource.password
#PostgreSQL Password for Insight server
jfis.db.password
#PostgreSQL Password for executor
jfex.db.password
#PostgreSQL Password for scheduler
jfsc.db.password
#Elastic search password
elastic.password


 


General Settings

Admins can modify the basic URL and default site assigned to Mission Control in the Onboarding Wizard in Admin | General Configuration.

  • No labels