JIMI Usage
Authentication
If authentication is on, optionally, there is also a captcha up front to stop any Denial of Service BOT attacks. Passwords are echo'd so not ideal. SSL Connections to your IM server should be used to minimise probabilities of compromise.
Commands
Commands are categorised, all commands can by listed by through the 'help' command. Current categories are:
Navigation
Command | Description |
|---|---|
help | lists all commands available, build dynamically so if a command exists, it will be listed |
quit | terminates the chat session |
logout | clears authentication status |
login | becomes authenticated with Captcha and Jira user authentication process, possibly changing user, possibly gaining access to restricted commands |
ls | Like unix 'ls', lists what virtual folder and files are at the current location |
cd | Like unix 'cd', changes the working directory, if an argument is given and it is a folder, the current location becomes that location. Arguments include '/' to go to the top of the tree and '..' to go up one level |
pwd | Like unix 'pwd', displays the present working directory if there was any doubt by the prompt |
Example navigation
Admin
Command | Description |
|---|---|
sysinfo | Executes the Jira System Info classes and dumps to console, RAM, PermGen, DB driver etc |
extysinfo | Executes the Jira System Extended Info classes, as above but more so |
Example Sysinfo (extssyinfo generates way too much)
Script
Command | Description |
|---|---|
{beanshell} | Taking liberties with Confluence markup, a post that starts with this command will be run through a Beanshell interpreter. Given this is inside a running Jira, it makes many things possible. Including trashing Jira. Care and Due Diligence a must. Currently any authenticated user could execute this command, to be fixed in the future |
Example {beanshell}
More commands will come, but feel free to request something if it scratches an itch.