Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
Red Hat Quay - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="red-hat-quay-jupiterone-integration-benefits">Red Hat Quay + JupiterOne Integration Benefits</h2> <ul><li><p>Visualize Red Hat Quay account, organization, organization members,<br> repositories, and teams in the JupiterOne graph.</p></li> <li><p>Map Red Hat Quay users to employees in your JupiterOne account.</p></li> <li>Monitor changes to Red Hat Quay users using JupiterOne alerts.</li> </ul><h2 data-id="how-it-works">How it Works</h2> <ul><li><p>JupiterOne periodically fetches account, organization, organization members,<br> repositories, and teams from Red Hat Quay to update the graph.</p></li> <li><p>Write JupiterOne queries to review and monitor updates to the graph, or<br> leverage existing queries.</p></li> <li><p>Configure alerts to take action when JupiterOne graph changes, or leverage<br> existing alerts.</p></li> </ul><h2 data-id="requirements">Requirements</h2> <ul><li>Red Hat Quay supports the OAuth2 Client Credential flow.</li> <li><p>JupiterOne requires a Bearer token. You need permission to create an<br> application in Red Hat Quay that will be used to obtain the API key.</p></li> <li><p>You must have permission in JupiterOne to install new integrations.</p></li> </ul><h2 data-id="permissions">Permissions</h2> <p>Access token must have the <code class="code codeInline" spellcheck="false" tabindex="0">user:admin</code>, <code class="code codeInline" spellcheck="false" tabindex="0">org:admin</code>, <code class="code codeInline" spellcheck="false" tabindex="0">repo:read</code>, <code class="code codeInline" spellcheck="false" tabindex="0">user:read</code><br> permissions</p> <h2 data-id="support">Support</h2> <p>If you need help with this integration, please contact<br><a rel="nofollow" href="https://support.jupiterone.io">JupiterOne Support</a>.</p> <h2 data-id="integration-walkthrough">Integration Walkthrough</h2> <h3 data-id="in-red-hat-quay">In Red Hat Quay</h3> <p><a rel="nofollow" href="https://access.redhat.com/documentation/en-us/red_hat_quay/3/html/red_hat_quay_api_guide/using_the_red_hat_quay_api#create_oauth_access_token">Create and OAuth Access Token</a></p> <ol><li>Log in to Red Hat Quay and select your Organization (or create a new one).</li> <li>Select the Applications icon from the left navigation.</li> <li>Select Create New Application and give the new application a name when<br> prompted.</li> <li>Select the new application.</li> <li>Select Generate Token from the left navigation.</li> <li>Select the checkboxes to set the scope of the token and select Generate<br> Access Token.</li> <li>Review the permissions you are allowing and select Authorize Application to<br> approve it.</li> <li>Copy the newly generated token to use to access the API.</li> </ol><h3 data-id="in-jupiterone">In JupiterOne</h3> <ol><li>From the top navigation of the J1 Search homepage, select <strong>Integrations</strong>.</li> <li>Scroll to the <strong>Red Hat Quay</strong> integration tile and click it.</li> <li>Click the <strong>Add Configuration</strong> button and configure the following settings:</li> </ol><ul><li><p>Enter the <strong>Account Name</strong> by which you'd like to identify this Red Hat Quay<br> account in JupiterOne. Ingested entities will have this value stored in<br><code class="code codeInline" spellcheck="false" tabindex="0">tag.AccountName</code> when <strong>Tag with Account Name</strong> is checked.</p></li> <li><p>Enter a <strong>Description</strong> that will further assist your team when identifying<br> the integration instance.</p></li> <li><p>Select a <strong>Polling Interval</strong> that you feel is sufficient for your monitoring<br> needs. You may leave this as <code class="code codeInline" spellcheck="false" tabindex="0">DISABLED</code> and manually execute the integration.</p></li> <li><p>Enter the <strong>Hostname</strong>, and <strong>Red Hat Quay Access Token</strong> generated for use by<br> JupiterOne.</p></li> </ul><ol start="4"><li>Click <strong>Create Configuration</strong> once all values are provided.</li> </ol><h1 data-id="how-to-uninstall">How to Uninstall</h1> <ol><li>From the top navigation of the J1 Search homepage, select <strong>Integrations</strong>.</li> <li>Scroll to the <strong>Red Hat Quay</strong> integration tile and click it.</li> <li>Identify and click the <strong>integration to delete</strong>.</li> <li>Click the <strong>trash can</strong> icon.</li> <li>Click the <strong>Remove</strong> button to delete the integration.</li> </ol><h2 data-id="data-model">Data Model</h2> <h3 data-id="entities">Entities</h3> <p>The following entities are created:</p> <table><thead><tr><th>Resources</th> <th>Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Entity <code class="code codeInline" spellcheck="false" tabindex="0">_class</code></th> </tr></thead><tbody><tr><td>Account</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_account</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Account</code></td> </tr><tr><td>Organization</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Organization</code></td> </tr><tr><td>OrganizationMember</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization_member</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">User</code></td> </tr><tr><td>Repository</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_repository</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Repository</code></td> </tr><tr><td>Team</td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_team</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">Team</code></td> </tr></tbody></table><h3 data-id="relationships">Relationships</h3> <p>The following relationships are created:</p> <table><thead><tr><th>Source Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> <th>Relationship <code class="code codeInline" spellcheck="false" tabindex="0">_class</code></th> <th>Target Entity <code class="code codeInline" spellcheck="false" tabindex="0">_type</code></th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_account</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization_member</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_repository</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_team</code></td> </tr><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_team</code></td> <td><strong>HAS</strong></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">red_hat_quay_organization_member</code></td> </tr></tbody></table> </article> </main>
.png)