Documentation Library

Search for information on Hornbill Documentation.


{{docApp.searchResultFilteredItems.length}} results for "{{docApp.currentResultsSearchText}}" in {{docApp.searchFilterBySpecificBookTitle}}

Have questions about this site?

What is this site?

  • This website is Hornbill's new product documentation website and is currently under development.
  • It is intended that all existing and future public-facing documentation we produce will be available to search, browse and share.
  • Hornbill's current documentation is available at Hornbill Wiki but over time this content will be migrated to this documentation site.
  • Please feel free to have a look around at any time.

Why has Hornbill created this site?

  • Hornbill's products have moved on considerably since we introduced it almost 10 years ago. At the time, the MediaWiki tool was sufficient, but we have outgrown it.
  • Our customers are more enterprise focused and more self-sufficient than ever before, so for 2023 and beyond we have established a new documentation platform and team to drive our documentation initiative forwards.
  • We are aiming to deprecate the use of Hornbill Wiki for most Hornbill related documentation.
  • We want to enable our growing partner network with product resources and information, documentation beyond our Wiki approach is required.
  • We could definitely do with some help, and may even pay for some! If you have domain knowledge and would like to help, please check out our Hornbill Docs Contributor Guide and contact the Hornbill docs team at

What will this site be good for?

  • Community contribution will be facilitated, encouraged, and most welcome.
  • High quality documentation, will be kept up to date as rapidly as our products evolve.
  • Real-time content search and discovery.
  • Articles organized into books, books into libraries, creating a more natural and logical structure to our documentation.
  • Legacy API documentation and various other documentation sources will all be consolidated into a single unified documentation system.
  • Documentation available in browser as well as printable/viewable as PDF on demand.
  • Personalized documentation experience, allowing dark/light mode, article subscriptions, social media sharing and other useful features.
  • Almost all publicly available documentation on will be open-source and available to fork on GitHub, allowing customers to derive their own custom documentation around Hornbill products should they wish to.

What is the timeline for this site?

  • We have taken the decision to publish and make available early, there is very little content at this time.
  • As and when we have completed/usable documentation, it will be published here.
  • We have a host of additional features we wish to add over time, so please watch this space.
  • We expect most of our existing documentation should be reviewed/migrated to over the coming months.
  • The documentation project will be ongoing, will continue to expand, evolve and improve day-by-day.

{{docApp.libraryHomeViewProduct.title ||}}


  1. {{book.title}}

{{group.title ||}}


  1. {{book.title}}


Users / Create

Operation Information

Creates an Active Directory user object via Adaxes.

This is a Premium Integration.


This operation requires authentication, the details of which can be securely stored on your instance in a KeySafe Key of type HTTP Basic Authentication (Username + Password).

To create a key of this type:

  • In the Configuration area of your Hornbill instance, navigate to Platform Configuration > Security > KeySafe;
  • Click on the + Create New Key button;
  • On the resulting Create New Key form, choose HTTP Basic Authentication (Username + Password) in the Type pick list;
  • Give the HTTP Basic Authentication (Username + Password) KeySafe key a Title (this is the name / identifier for the HTTP Basic Authentication (Username + Password) account as you will see it when using the cloud automation node in your workflows);
  • Optionally populate the Description field;
  • Populate the following fields accordingly, then click the Create Key button to create your new key:
Name Type Description
Username string Authentication Username
Password string Authentication Password
API Endpoint string Optional API Endpoint


The API Endpoint field should be populated with the Adaxes server address & endpoint, in the format: https://adaxes.externally.facing.address/AdaxesSpmlWS/SpmlProvider.ashx.

As Adaxes is an on-premise tool, and not in the cloud, the following rules should be adhered to:

  • The Adaxes SPML endpoint will need configuring in IIS to support Basic Authentication;
  • Traffic to/from the Adaxes SPML endpoint will need to be over SSL - so as to not send Basic auth details without encryption;
  • You will need to configure your firewall to allow traffic over port 443 from the iBridge IP address ( to the externally-facing IP address of your Adaxes web server.

Revoking Access

If at any point you wish to revoke access to any of the above accounts from your Hornbill instance, just delete the relevant KeySafe key(s) from the KeySafe list.


This will revoke the rights of any existing Cloud Automation Node in your Hornbill Workflows that are using the revoked HTTP Basic Authentication (Username + Password) account, so you will need to manage these workflows accordingly.

Input Parameters

Display Name ID Type Description Required Supported Values
Container ID containerID string ID of the Container to create the new Object in Yes None provided
CN cn string CN Yes None provided
S AMAccount Name sAMAccountName string S AMAccount Name Yes None provided
Enabled? enabled boolean Should the new account be set as enabled? No None provided
Description description string Description No None provided
Given Name givenName string Given Name Yes None provided
SN sn string SN Yes None provided
Initials initials string Initials No None provided
Display Name displayName string Display Name Yes None provided
Mail mail string Mail No None provided
Mail Nickname mailNickname string Mail Nickname No None provided
Telephone Number telephoneNumber string Telephone Number No None provided
Mobile mobile string Mobile No None provided
Home Phone homePhone string Home Phone No None provided
Department department string Department No None provided
Title title string Title No None provided
Manager manager string Distinguished Name of users Manager No None provided
Company company string Company No None provided
Physical Delivery Office Name physicalDeliveryOfficeName string Physical Delivery Office Name No None provided
W WWHome Page wWWHomePage string W WWHome Page No None provided

Output Parameters

Display Name ID Type Description
Status status string Return Status
Distinguished Name distinguishedName string Distinguished Name
Object GUID objectGUID string Object GUID
User Principal Name userPrincipalName string User Principal Name
In This Document