Page Comparison

Each User and their associated Permissions configured in Iguana X are stored in the users configuration directoryThe users configuration directory contains a separate directories for each User configured in IguanaX:

Code Block
<instance<working directory>/configurationsconfig/users/

...

<USERNAME>

Within each distinct User’s directory, there will be multiple files containing User specific configurations:

Expand

title	usersuser.json config contains the username, password and description tags (assigned #permissionroles #tags)

usersuser.json config contains the username, password and description - the assigned #permission Roles #tags. All passwords are encrypted. The file will look something like:

Code Block

language	json

{
    "adminpassword": {
   "87evesKSFSgZhzQicA3QvIhB1IBc1rTJAtfUTTQtIGQQwWa4jH3eFciZUEKAf1s",
    "descriptionroles": "#admin",[
        "password#admin":
"TaLkTwYBJW9yRyTeDoFTsxmqHm4gM7tLZ06Myvj7XgaWluYwxMVofHqox5OYa6gG70E556CB57CF27B1BC58ECA092EF85EB7BEA91D30D95A1433DF18E101F8A368C6E9BF6C3E943EC5A09720A6EAFB6836A345AD4A004B2D18850B3A9CDED388044",    ],
    "username": "admin"
    },
    "support": {
   }

The Role settings are stored in an encrypted roles.json file located in:

Code Block
<working directory>/config/settings/roles.json

Expand

title	filter_tags.json contains the user specific Dashboard Filter Tags

Each User can configure unique quick Filter Tags on their IguanaX Dashboard. These filter tags are stored in the filter_tags.json file. For example:

Code Block

language	json

["#demo","#hl7","#fhir","#training"]

permissions contains the permission details configured for each hashtag

Expand

title	Git configuration files required to interact with the git host service are stored in each User directory

Each user directory will be named according to the configured user.

For example, every Iguana instance will have an admin directory containing the admin information required to interact with the configured Git host service.

git.json - Iguana generates this configuration file to store your selected Git service, username, and token so that Iguana can create repositories within your Git service.

Code Block

language	json

{
    "descriptionservice": "#supportBitbucket",

       "passwordtoken": "Ko1eSFUaz86h7EXYlMEPrbGNdyobdtlFa9O66atyHYcb2mQv3W9kyjgoQR7R7RZf7F5DCAFA65ED94FF87ADB15AB489ECF14752CB5053AE9D9074A118F1EB8135187D48BC06EE422E919192FCCEA288C2B5ABF8253F526843DA8266C25E3BC80A04628908105F9SFSF8982F5CF4AEA30F2909A9A1B2F8F99CA66C4FA",
  
     "username": "supportj_john"
    }
}

Expand

title

owners.json

permissions.json contains each #permission and the assigned access level

- Iguana stores the group of repositories you have access to within your Git Service. For example, your Bitbucket workspaces.

Code Block

language	json

{[
    "#admin":j_john",
    "Write",
    "#support": "Control"
}

Expand

title	Each user directory contains the configured git information required to interact with bitbucket

Each user directory will be named according to the configured user. For example, every Iguana instance will have an admin directory containing the admin information required to interact with Bitbucket. This provides Iguana the information to label commits made in the Translator according to specific users and enforce git permissions (read/write permissions on Bitbucket repositories)

interfaceware"
]

gitconfig - Iguana stores the ssh command and Author Info used to label commits, authenticate and interact with your Git repositories from the Translator.

Code Block

language	json

[core]
	sshCommand = ssh -o "StrictHostKeyChecking=no" -o "IdentitiesOnly=yes" -i "'C:/ProgramData/IguanaX2/config/users/admin/privatekey'"
[credential "http://18.218.2.204"]
	provider = generic
[user]
	email = j.john@interfaceware.com
	name = John

privatekey and privatekey.pub - Iguana generates and stores your SSH Key pairsfilesused to authenticate with your git service in the Translator.

Versions Compared

Old Version 2

New Version Current

Key