With our product roadmap we share our vision of the future of Adaxes and reveal the main features we are planning to implement. We would love to see your contributions, which you can provide by upvoting the features in the list and by submitting new suggestions via this form.
Please note that the Adaxes roadmap is just a preliminary plan, so the order of implementation might change and not all the features listed below may make it into the final product.
Allow dynamic updates of forms in Web Interface. For example, change which fields are displayed on the user creation form based on the Employee Type property or depending on which Department is selected, alter the values in the drop-down list for the Job Title field.
Allow the management of pure cloud environments that run in the Microsoft Azure cloud platform.
Make it possible for Mac users to reset their AD password from the macOS login screen.
Add an option to use Adaxes as a Software as a Service (SaaS) application hosted in the Microsoft Azure cloud.
Add a possibility to add members to groups for a limited amount of time.
Allow users to bulk import Active Directory objects from CSV files via the Web Interface.
Add an option that will allow users to choose between receiving a code via SMS or using an authenticator app when they reset their forgotten password (if both methods are enabled).
Make it possible to access Adaxes functionality programmatically and perform operations in Active Directory through a REST API.
When entering a new password in the Web Interface, display additional information, e.g. if the entered password is weak or strong, whether all requirements are met, etc.
Allow specifying properties that need to have unique values with the help of Property Patterns and define what needs to be done if a value is not unique. For example, automatically add a digit at the end of an entered username if such a value already exists.
Add an option to Property Patterns which allows generating property values with the help of scripts. For example, automatically generate a custom username on the user creation form using a PowerShell script.
Add more options for drop-down lists. For example, automatically put in all the existing values of the Department property as values of the drop-down list when creating or editing user accounts.
Allow filtering AD structure in tree views, e.g. in the browsing drop-down, similarly to how it’s done in list views.
Allow replacing and removing specific characters when generating values with the help of Property Patterns, e.g. always replace ä, ö, ü with a, o, u.
Similarly to cutting a certain number of symbols from the beginning of a property value, like getting the first letter of the First Name with %firstname, 1%, also allow cutting a number of symbols from property values from the end.
Allow specifying From, CC, BCC fields, setting Sender Name and adding attachments for the ‘Send e-mail notification’ action in Business Rules, Custom Commands and Scheduled Tasks.
Allow updating the operations that were already sent for approval. For example, if an approver notices a mistake or needs to provide additional information for the operation, let them introduce the edits before approving.
When an operation is sent for approval, allow the initiator to specify the reason for why the operation needs to be executed.
Add unique identifiers to be associated with each approval request, so that it’s possible to easily find specific requests and refer to them using their IDs.
In addition to object owners specified in Active Directory, also allow specifying co-owners for AD objects.
Send notifications about already existing approval requests when new approvers are added. For example, if users are added to a group which allows them to approve or deny requests that are awaiting approval, send a corresponding email notification to them.
Add support for HTML-formatting of emails, such as Enrollment Invitations and Reset Password notifications.
Similarly to sending actions for approval to group owners, also allow sending approval requests to co-owners who are specified via ms-Exch-Co-Managed-By-Link.
Add options to authenticate Adaxes in Microsoft 365 with a client certificate or App password in place of using credentials of an Microsoft 365 account.
Add an option to use SSL encryption for all communication between Adaxes and managed AD domains.
Allow storing AD objects in Adaxes virtual properties the same way data is stored in properties like CustomAttributeText1 or CustomAttributeBoolean1.
Allow users to modify objects in bulk in the Web Interface, for example, to set a manager, change account expiration date or enable smartcard authentication for multiple users in one go.