Community
Questions Library
Docs
Blog
Events
Swag
Github
Slack
JupiterOne
Discussions
Release Notes
Contact Us
JupiterOne 28 January 2022 Release - AskJ1 Community
<main> <article class="userContent"> <p>January 28, 2022</p> <h2 data-id="new-features-and-improvements">New Features and Improvements</h2> <ul><li>"Get links to your accounts" on the sign-in page now provides a list of all accounts associated with your email address, not just single sign-on accounts. This change makes the sign-in experience easier for users with multiple accounts.</li> </ul><h2 data-id="integrations">Integrations</h2> <h3 data-id="google-cloud">Google Cloud</h3> <ul><li><p>Added new properties to entities.<br></p><table><thead><tr><th>Entity</th> <th>Property</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">google_iam_service_account</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">active</code></td> </tr></tbody></table></li> <li><p>Fixed an issue where <code class="code codeInline" spellcheck="false" tabindex="0">_key</code> value was not properly assigned to deleted <code class="code codeInline" spellcheck="false" tabindex="0">google_compute_image</code> assets.</p></li> <li>Fixed an issue where <code class="code codeInline" spellcheck="false" tabindex="0">_key</code> value was not generated properly. This fix allows for correct mapping of <code class="code codeInline" spellcheck="false" tabindex="0">google_iam_binding</code> to <code class="code codeInline" spellcheck="false" tabindex="0">google_query_table</code> when creating <code class="code codeInline" spellcheck="false" tabindex="0">google_iam_binding_allows_resource</code> relationships.</li> </ul><h3 data-id="azure">Azure</h3> <ul><li>Added new properties to entities.<br><table><thead><tr><th>Entity</th> <th>Property</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">active</code></td> </tr></tbody></table></li> </ul><h3 data-id="npm">NPM</h3> <ul><li>Improved error handling response when NPM registry API returns a 429 error.</li> </ul><h3 data-id="github">GitHub</h3> <ul><li><p>Added new properties to entities<br></p><table><thead><tr><th>Entity</th> <th>Property</th> </tr></thead><tbody><tr><td><code class="code codeInline" spellcheck="false" tabindex="0">github_user</code></td> <td><code class="code codeInline" spellcheck="false" tabindex="0">active</code></td> </tr></tbody></table></li> <li><p>Truncated potentially large <code class="code codeInline" spellcheck="false" tabindex="0">body</code> and <code class="code codeInline" spellcheck="false" tabindex="0">bodyText</code> property values from <code class="code codeInline" spellcheck="false" tabindex="0">github_issue</code>.</p></li> <li>Removed <code class="code codeInline" spellcheck="false" tabindex="0">body</code> and <code class="code codeInline" spellcheck="false" tabindex="0">bodyText</code> property values from <code class="code codeInline" spellcheck="false" tabindex="0">github_issue</code> raw data.</li> </ul><h3 data-id="jira">Jira</h3> <ul><li>Added support for Jira API Version 2 (Jira Data Center 8.20.3).</li> <li>Added support for specifying the port in the <code class="code codeInline" spellcheck="false" tabindex="0">jiraHost</code> configuration file (such as <code class="code codeInline" spellcheck="false" tabindex="0">example.com:8080</code>).</li> <li>Added optional bulk ingestion feature to allow for collecting every single issue in a Jira project. This feature currently requires someone at JupiterOne to activate.</li> <li>Added <code class="code codeInline" spellcheck="false" tabindex="0">Issue</code> class to <code class="code codeInline" spellcheck="false" tabindex="0">jira_issue</code> entities.</li> <li>Added error handling for <code class="code codeInline" spellcheck="false" tabindex="0">Issue</code> ingestion to avoid one bad <code class="code codeInline" spellcheck="false" tabindex="0">Issue</code> causing the step to fail.</li> </ul><h2 data-id="coming-soon">Coming Soon</h2> <ul><li>Compliance Version 2.0: Major updates to the J1 Compliance app are in progress, and are planned for release next week. This new version includes the centralization and reusability of controls, a new look-and-feel, and improved navigation within the app.</li> </ul> </article> </main>