Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
Integration and mapping related FAQs - AskJ1 Community
<main> <article class="userContent"> <h2 data-id="how-do-i-get-my-custom-on-premise-data-into-jupiterone">How do I get my custom / on-premise data into JupiterOne?</h2> <p>JupiterOne's asset inventory, search and visualization supports any data imported that follows the <a rel="nofollow" href="../jupiterOne-data-model/jupiterone-data-model.md">reference data model</a>, not limited to data ingested by managed integrations.</p> <p>This is easily done via the API or CLI. Each entity object can be represented in a few lines of JSON or YAML code. The <a rel="nofollow" href="../APIs/j1-client-and-cli.md">J1 API Client or CLI</a> can create/update them to your JupiterOne account. You can also develop a script to run on a schedule (such as via a cron job) or integrate into your DevOps automation.</p> <h2 data-id="where-do-these-person-entities-come-from-why-are-they-not-tagged-with-an-integration">Where do these <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code> entities come from? Why are they not tagged with an integration?</h2> <p>The Person entities are “mapped” from <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">User</code> entities. They are considered "shared" entities that multiple integrations can map to and contribute properties to. For example, a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code> can be created by a Google integration (from a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">google_user</code>). Or from a Github User, AWS IAM User, etc.</p> <p>The <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code> entities represent actual individuals in the organizations, whereas the <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">User</code> entities are the logical user accounts within each digital environment/account (i.e. from an integration).</p> <h2 data-id="how-are-person-entities-i-e-employees-created">How are <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code> entities (i.e. <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">employees</code>) created?</h2> <p>A <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code> entity is created by the "mapper" process -- when a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">User</code> entity is ingested/updated from an identity provider integration (e.g. Okta, OneLogin, Google), a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code> entity is "mapped" with the user's information (first and last name, email address, etc.).</p> <h2 data-id="how-can-i-avoid-creating-a-person-entity-for-a-generic-system-user-account">How can I avoid creating a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code> entity for a generic/system user account?</h2> <p>Certain properties are used to determine if the user is a system user or an actual individual. This depends on the integration.</p> <p>For <strong>Okta</strong>, you can set the <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">userType</code> property for the user to one of the following to avoid it being mapped to a <code class="code codeInline code codeInline" spellcheck="false" tabindex="0">Person</code>:</p> <ul><li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">bot</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">generic</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">service</code></li> <li><code class="code codeInline code codeInline" spellcheck="false" tabindex="0">system</code></li> </ul> </article> </main>
.png)