Mikesh 3.0

Introduction

This readme contains system requirements, an installation guide, troubleshooting advice and contact information. For API documentation, refer to MikeshSyntax.html. While the server is running, interactive API documentation is also available locally at http://<host>:<port>/docs/.

Requirements


 
 
 
 
Supported platforms Mac (Big Sur 11 or later)
Windows (10 or later)
Linux (Kernel 3.2 or later, tested on Ubuntu)
Supported architectures x86_64, arm64
Minimum hardware requirements Processor >= 1GHz
RAM >= 1GB
Ethernet >= 100Mbit

Installation

To install Mikesh, use the appropriate installer for your platform.

macOS

Double-click the MikeshInstaller.app from Finder and follow the instructions.

Windows

Firstly, modify config.toml in your favourite text editor to configure the service, then double-click the MikeshInstaller.exe from File Explorer and follow the instructions.

Ubuntu

From terminal, navigate to the installer and run

$ bash Install.sh

In any case, the installation requires administrator privileges.

Installation Directory

Platform Path
macOS /Library/Application Support/24U/Mikesh
Windows C:\Users\Public\24U\Mikesh
Linux /opt/Mikesh

Entra ID setup

For Entra ID, you need to authorize Mikesh in the Azure Portal in order to obtain the client id and secret. To this end, go to Azure Portal and login as the administrator. Then

  1. Select Microsoft Entra ID service.
  2. Go to “App registrations”.

  1. Add a new registration and name it Mikesh. (It is recommended to use the default settings.)
  2. Click on the Mikesh registration overview and copy the client id.
  3. Go to “API permissions” and add the following application permissions:
  4. Grant admin consent for your Directory.
  5. Go to “Certificates & secrets”. Generate a client secret for Mikesh. Store the secret e.g. in you keychain. (It will disappear after a while with no option of recovery.)

Troubleshooting

1. Endpoints cannot be called from a different device

Firstly, verify that config.toml file has ip set to 0.0.0.0 (wildcard) and not 127.0.0.1 (localhost). On Ubuntu and Windows, communication can fail silently because of firewall. To allow a port, run

Platform Command
Windows New-NetFirewallRule -DisplayName “Mikesh 24U” -Direction Inbound -Protocol TCP -LocalPort 24034 -Action Allow
Ubuntu sudo ufw allow 24034/tcp

(Replace 24034 with your port number in case you are not using the default value.)

2. Strong Auth Required Error

This error message

 "LDAP Result Code 8 \"Strong Auth Required\": 00002028: LdapErr: DSID-0C090343"

appears when you try to connect with LDAP to an Active Directory server which requires LDAPs. You can revoke the signing requirements by running gpedit.msc. Go to Windows Settings -> Security Settings -> Local Policies -> Security Options. Set:

A more secure approach is to change the url (passed to Mikesh) from “ldap://hostname:389” to “ldaps://hostname:636”. This requires the directory server be equipped with a valid SSL certificate.

3. Invalid character Error

If you see this type of error (on Windows)

{
    "error_code": 400,
    "error_message": "invalid character U in string escape code"
}

check that the file paths in the json parameter do not contain single backslashes. In JSON, backslash is a string escape character. Therefore, you must replace backslashes with double backslashes. (Forward slashes also work.)

C:\Users\johndoe\Documents Error
C:\\Users\\johndoe\\Documents OK
C:/Users/johndoe/Documents OK

4. Groups in FileMaker are not split

The columns groups in user output uses vertical tab as a delimiter. In FileMaker, vertical tab (Char( 11 )) is treated as an invisible symbol. It means you will not see any separator in a TextField or a DataViewer. However, FileMaker can parse the symbol under the hood. For instance, you can replace it with a carriage return symbol using

Substitute ( $groups ; Char( 11 ) ; ¶ )

just like with any visible symbol.

5. User data contains mangled symbols

User attributes often contain non-ASCII characters. Whenever you use the Import Records script step in Filemaker, make sure you select UTF-8 character encoding. Otherwise, the data will not be parsed correctly.

Shareware Notice

Please note that Mikesh is shareware. That means it is not free, and you have to pay a license fee if you want to keep it. You can install this plug-in and try it out for the period of 14 days. After this period, ProductName can stop working and require a registration code. You will get your registration code after you pay for your license.

You can freely distribute Mikesh as long as you distribute the original compacted archive untouched, and you don’t charge money for the distribution. If you want to distribute ProductName on a physical medium, such as flash disk, or if you want to distribute it in other form than the original compacted archive, you must ask for our permission. If you are a solution developer and want to bundle ProductName with your products, please contact 24U Software.

Please find detailed registration instructions in the file named HowToRegister.html.

Contact Information

You can contact us at one of the following addresses. We prefer being contacted by email, but you can use any other method of your preference:



24U Software
The software Mikesh is copyright ©2001-2026 24U Software. All rights reserved.