Jimi is an automation first no-code platform designed and developed originally for Security Orchestration and Response. Since its launch jimi has developed into a fully fledged IT automation platform which effortlessly integrates with your existing tools unlocking the potential for autonomous IT and Security operations.
A bug after released was identified that prevented installation 3.041 fixes this bug
Working organisation setttings page which allows for control over security policies including passwords and authentication types
JIMI now supports LDAP for authentication! In order to get started you'll need to define a connection in the organisation settings page (after enabling LDAP). You'll then need to define a user with "ldap" as their login type.
My Account now includes a dropdown menu for theme selection. No more guessing what the theme names are
Added UI options for file tokens and downloading of already uploaded files
Object revision UI is no longer in BETA and now is officially released. As part of this release the UI has been updated to include the revision creator as well as a view button that enables you to see the content of the revision without restoring the object
Added message to worker killed exception to make it clear that the failure on the status page was caused by the system killing the trigger
The status page polling improved to reduce network utilization
Fixed a bug within the cluster checksum and update system that meant users had to update multiple times before it would be successful
An issue that caused the health checker service to crash has been resolved
Users now have the ability to change themes, this can be done through the My Accounts page
Ability to change name and email address associated
Whats New ( This ) panel has been added to inform users of changes after an upgrade has taken place. Once a user pressing the "Close" button the panel will not be visible until the next upgrade
User and Group status is now enforced
CLI reset of root user no longer requires waiting the lockout period to expire
Status page list of triggers now supports right click to clear startChecks which will restart a trigger
Save dialogs now appear down the bottom right of the screen instead of as banners
Changes made to objects are now stored within the revision system to enable quick and simple restore of previous versions.
Within ConductsEditor right click on an object and select "Revision History"
Viewable last 100 execution times for a trigger
Within ConductsEditor right click on an object and select "Statistics"
Welcome to jimi version 3.
This release brings with it major changes both within the backend and frontend UI:
Working organisation setttings page which allows for control over security policies including passwords and authentication types
JIMI now supports LDAP for authentication! In order to get started you'll need to define a connection in the organisation settings page (after enabling LDAP). You'll then need to define a user with "ldap" as their login type.
My Account now includes a dropdown menu for theme selection. No more guessing what the theme names are
Added UI options for file tokens and downloading of already uploaded files
Object revision UI is no longer in BETA and now is officially released. As part of this release the UI has been updated to include the revision creator as well as a view button that enables you to see the content of the revision without restoring the object
Added message to worker killed exception to make it clear that the failure on the status page was caused by the system killing the trigger
The status page polling improved to reduce network utilization
Fixed a bug within the cluster checksum and update system that meant users had to update multiple times before it would be successful
An issue that caused the health checker service to crash has been resolved
Users now have the ability to change themes, this can be done through the My Accounts page
Ability to change name and email address associated
Whats New ( This ) panel has been added to inform users of changes after an upgrade has taken place. Once a user pressing the "Close" button the panel will not be visible until the next upgrade
User and Group status is now enforced
CLI reset of root user no longer requires waiting the lockout period to expire
Status page list of triggers now supports right click to clear startChecks which will restart a trigger
Save dialogs now appear down the bottom right of the screen instead of as banners
Changes made to objects are now stored within the revision system to enable quick and simple restore of previous versions.
Within ConductsEditor right click on an object and select "Revision History"
Viewable last 100 execution times for a trigger
Within ConductsEditor right click on an object and select "Statistics"
Welcome to jimi version 3.
This release brings with it major changes both within the backend and frontend UI:
My Account now includes a dropdown menu for theme selection. No more guessing what the theme names are
Added UI options for file tokens and downloading of already uploaded files
Object revision UI is no longer in BETA and now is officially released. As part of this release the UI has been updated to include the revision creator as well as a view button that enables you to see the content of the revision without restoring the object
Added message to worker killed exception to make it clear that the failure on the status page was caused by the system killing the trigger
The status page polling improved to reduce network utilization
Fixed a bug within the cluster checksum and update system that meant users had to update multiple times before it would be successful
An issue that caused the health checker service to crash has been resolved
Users now have the ability to change themes, this can be done through the My Accounts page
Ability to change name and email address associated
Whats New ( This ) panel has been added to inform users of changes after an upgrade has taken place. Once a user pressing the "Close" button the panel will not be visible until the next upgrade
User and Group status is now enforced
CLI reset of root user no longer requires waiting the lockout period to expire
Status page list of triggers now supports right click to clear startChecks which will restart a trigger
Save dialogs now appear down the bottom right of the screen instead of as banners
Major new release with a significant UI changes
Changes made to objects are now stored within the revision system to enable quick and simple restore of previous versions.
Within ConductsEditor right click on an object and select "Revision History"
Viewable last 100 execution times for a trigger
Within ConductsEditor right click on an object and select "Statistics"
Welcome to jimi version 3.
This release brings with it major changes both within the backend and frontend UI:
Major new release with a significant UI overhaul and core improvements
Due to the size of the update we have only included the key changes, checkout the commit history for more details on other improvements and changes.
Docker upgrades will required the placement of a new public and private key for the web server:
Run the following within the data directory
openssl req -newkey rsa:2048 -nodes -keyout web.key -x509 -days 365 -out web.cert
This is a servicing release to fix a number of bugs present within v1.5