> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/step-by-step-onboarding-guides/rpm-no_scm-no_sca-local-artifact_server_no_jfrog-keep_names.md).

# Step-by-Step Setup Guide

This guide walks you through the initial account setup, token generation, and connecting your first project to Seal Security.

## Account Creation & Token Generation

Follow these steps to access the platform and prepare your environment. If you already have a token, you can skip to the next section.

1. **Access the Invite:** Click on the **Sign in >** button in the Seal Security invite email you received.
2. **Log In:** Log in to the platform using your password or social login credentials.
3. **Start Onboarding:** We're starting the onboarding flow. Click **Next >** to begin.
4. **Generate Token:** First, you must generate a token to Seal's artifact server. This allows you to download our sealed versions.\
   ![Generate Token](/files/PavZ4q5NrXJse1vkrR0Y)
   1. **Generate:** Click on **Generate token**.
   2. **Copy:** Copy the newly generated token using the copy icon at the right of the text box.

      > **Important:** You will need this token later. While it should eventually be saved in a secure location (like a password manager or secret store), copy it now for immediate use in the next steps.
   3. **Download CLI:** Download the appropriate CLI binary for your machine.
   4. **Continue:** Click **Next >**.
5. Click **Maybe later** to skip the GitHub integration.
6. **View Protection page:** You will land on the Protection screen.
   * **Status:** Since no projects are connected yet, we are not showing any results.
   * **Next Step:** We are now going to populate this data using the CLI. ![Empty Protection page](/files/Fgf0cjrcjNzbEzFu4thb)

## Configure the Artifact Server

To pull sealed versions, you must configure your environment to trust and prioritize Seal's repository. Choose the scenario that matches your infrastructure.

### Prerequisites

In all configurations below, you will need the following values:

* **`$SEAL_TOKEN`**: The Access Token you generated in the onboarding flow.
* **`$SEAL_PROJECT`**: Your Project ID (e.g., `my-first-project`). This is used for reporting usage.

### Configuration Steps:

Yum's configuration is saved in the `yum.repos.d` directory.

1. Create a file with Seal's GPG key by creating `/etc/pki/rpm-gpg/RPM-GPG-KEY-SEAL-SECURITY` with the following content:

   ```
   -----BEGIN PGP PUBLIC KEY BLOCK-----

   mQGNBGSAaCABDADjpSHVbpNQoVIwWuxPwK7L/8HyKEhalyNOp0JWIUGKkC+3yxkq
   B6c1DBeaA1nrE+J65PUjEfm2exngqFddfGCV4HlVweB99Ojsfa0Lxg1RfUvsYd1+
   lt8VDf1/iSadQRmukc9e6n+ijsnZ6603T2EHyVCWeMjoAbUjDxvj+mgzYxAlkg+X
   BsPULgQ9WZyyeNCOTOZcO02Oo2WHFseAPKl+9ydvCbmr+l3ZFOJH5BWiY5eazhaf
   yPB7W18eQr4XCPFnH4rgt2tl7oBUKaShgb6tHzTIb6+NQmJ7ZsjZi8WoLRoHo/q+
   SCHzrx361YMN6sNmr+DighHNjA8UTLM1odj+y0i4h4eKexmY1n/PvP3ZTaMSTdrc
   s09lu2bzhlOlt2WpL5I9EJMbt0HjUTMMVuwZFYy2/X5ZZhFXM05kozvnaXLGqHfI
   u7Lkr1nnmk3icBRfL6LB977m8MtglEW5K4YnKudSmxwFmnTXCtGP1Mwjul+kOZgO
   CkEKknfPoGPZemsAEQEAAbQkU2VhbCBTZWN1cml0eSA8aW5mb0BzZWFsc2VjdXJp
   dHkuaW8+iQHUBBMBCgA+AhsDBQsJCAcCBhUKCQgLAgQWAgMBAh4BAheAFiEEshGJ
   maGpsrx9Q6ddM/H1NVGm4GkFAmfJakQFCRYVBSQACgkQM/H1NVGm4Gmawgv/Y0Ml
   zm4tWyptkZ+5AJ97C4jL6WvEN0IDxkbYH8YdsHHc2exv1EVBqtRvY+06pjVC5OIx
   zt10Cqk1kENQPibZO5K8wIWJdKemJoZl4soGSrinLLjwyyvl84bwUE/1oiQHrUn1
   Kf1RH2GKkVnD0R8oRwohpzCNDOukgbQ7dp+p5JZuBB9YB+KvdR2XHwcGyzE8HSgr
   vNroKTpYdmtFejeBfKcA2BTt/bS0zq4XWD0LTHkwZMVvDK/5QOH4KPjFoipDz3EF
   +TXvy/AYtEd1mhjqKgU5r+FgHgaqZJVH8W2a08p/OJ3W/ML3jEL+LJbbVPY5XYPe
   NeGZW5Z/WnedC4mY0V/MlyPdY4Gcqv8oIU32vsfLDSpIrmK5Li86+aSlve+OUG51
   We/XKCmBrZ5AS6tCeMdvIitbreE495JAhw4ZKbjqx9SN7ehZ6lXEasx8BZNm+Fpx
   l0+EJYJ4ATjKpgvW3BJzj+aiRJGXT7rjw25/OE7ydHtV9kcyuMYtTmKYkguSuQGN
   BGSAaCABDADO445QG3oM3EF2UrjG6oIQ893APlfPK1/vjCzV/PFUb0au9VPacFaT
   m+e9dUrhX0ghL9yiZJTposIS/EEEZeRO6TvSgDdXG5P5A8Y4jdQSEvoHewsmraQj
   E+oFLf2g5WsGJ4YOSmN/2b429cBSLk3Blp+Pz0ajL4rS4xC6JP26qLdkmmjHlG86
   hAyn2t0wDVHy4+tgbe/Dx1B0mE1PLNA4x9wGlSQMTA/GQbwTGp/+UJ9ss9UgMxOm
   zpnBgarS2qZDc/eY88TeX2kxCEDwheYyPYc18DiH419pnJTqHSN+6W7oMYymrRwP
   77R9c7D+EDGXIUVWqvAlfn5HF6szIL5fKpkyDFy5+wCukX2vihvRyIqedj7/rFvY
   rBT/yhQPpnuaGNvwBEaKQJP8lhj3Ldb34RkY5exBbIGJujkgtByI2c69B0VZXzs+
   sTP42JVLW6ZhqjFR0nllbq9GantNipMaXd3XCBNCJRAu+xIypCv9K35i7QAUhyPA
   HiClcaSabQ0AEQEAAYkBvAQYAQoAJhYhBLIRiZmhqbK8fUOnXTPx9TVRpuBpBQJk
   gGggAhsMBQkDwmcAAAoJEDPx9TVRpuBpa1YL/j9+51s++kEIh8iJxHmBbEwR1i7a
   J30ouN/+qFJgd2PwX8s0xh0iVeRjVugEh7ZTIs+rcJS6k2K6BA9AKJBDDBl4YOT/
   m8VzUBLc7C/NsWdzK9UYkYd/mHMw6vYsfgWZt/FN08dd94REC1rE8emtyJmav5qK
   4SDnqbiZG8cjN0ifM78jUo5fwU6c1q3tGXn6NXivyfBl7rt/We8bhAyPtA503ABB
   yqt+jZQQfOmeVehOT/IHP6aHYVyy6CRC+BWOYzfmtl095sARN7Ft+zWiw8Z3wJX3
   mTK31dGBzqA/4Z8yKB0btngH8qh5afV7PaQxVzSFwjpQM53hrnycHHOi4STettM2
   EWQDuo3R4Y6jZYG8moszxbvfsJSWJqKMHYtcGU8HTsXEAcuNegF66R5QqFi7u7am
   olXTp1bTRVeMd17V7KR5/YhYCAae5Rsex0zfLYBfPLdttSlpds9dlTiTyRDoh3gf
   oA1Luccjce+NjWspiLHFrV/OllSlRSuKyf+LqA==
   =meVJ
   -----END PGP PUBLIC KEY BLOCK-----
   ```
2. Identify the name of the distribution using the ID field in the output (for example: centos, rhel, etc.):

   ```bash
   cat /etc/os-release
   ```
3. Create a new file `/etc/yum.repos.d/seal.repo` with the following content:

   ```ini
   [seal]
   name=seal
   baseurl=https://rpm.sealsecurity.io/<DISTRO>/$releasever/seal/noprefix/$basearch/
   username=$SEAL_PROJECT
   password=$SEAL_TOKEN
   enabled=1
   gpgcheck=1
   gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-SEAL-SECURITY
   ```

## Sealing a package

Once you have integrated the Seal artifact server into your pipeline, follow these steps to see the results.