Provisioning

As an HelloID administrator it would be nice to have an integrated solution to generate a secure link to provide the user's password after creation. Something like : onetimesecret.com

Currently, the CorrelationConfiguration is not available in the uniqueness check script through the ActionContext . Because of this, when performing uniqueness checks in correlation scenarios, the correlation values need to be manually defined in the uniqueness check script. Why this is a problem The same configuration effectively needs to be maintained in two places: The Correlation Configuration of the target system. The uniqueness check script. When correlation attributes are added or changed, the uniqueness check script must also be updated manually. This creates duplicate configuration and makes it easy to overlook one of the locations. If these configurations become inconsistent, uniqueness checks may behave incorrectly. For example, during a correlate scenario with a unique value without iteration, the uniqueness check may incorrectly detect the person's own account as a conflict. Suggested Improvement Make the CorrelationConfiguration available in uniqueness check scripts through the ActionContext . This would allow the uniqueness check script to dynamically use the configured correlation attributes instead of requiring them to be manually duplicated. This would: Prevent duplicate configuration. Reduce the risk of configuration inconsistencies. Make uniqueness check scripts more generic and reusable across connectors. Prevent issues when correlation attributes are changed without updating the uniqueness check script. In short: expose the CorrelationConfiguration through the ActionContext so uniqueness check scripts can use the configured correlation values directly.

Currently, Rule Mining analyzes all imported entitlements that are present in a target system. In practice, some entitlements should not be considered when creating Business Rules. Permissions may, for example, be outdated, intended for manual assignment, or otherwise irrelevant to business rules. Rule Mining can still identify patterns for these entitlements, causing them to appear in the Rule Mining report and adding unnecessary results to the analysis. We would like to introduce an exclusion list for entitlements in Rule Mining. Administrators should be able to select specific entitlements from a target system and exclude them from Rule Mining. Entitlements on this exclusion list should not be analyzed and should not appear as results in Rule Mining reports. This would: Reduce irrelevant results in Rule Mining reports. Allow administrators to focus the analysis on entitlements that are actually candidates for Business Rules. Prevent outdated or otherwise irrelevant entitlements from influencing the Rule Mining analysis. Make Rule Mining reports easier and faster to review.

With the new Entitlement overview we can see all business rules belonging to an entitlement. I would like to have the option to directly remove all occurrences of the entitlement in all the business rules, especially for the entitlements no longer available in the target systems. I spend the entire morning clicking to remove all occurrences while there where only 31 entitlements to remove.

Allow an export option within Business rules editor. Where the rules are being built and the list of users isshown on the right side of the screen. Could this be exported for external validation in other systems? Many thanks in advance.

Lately, we see an increase of errors on the Active Directory target connector saying "A connection to the directory on which to process the request was unavailable. This is likely a transient condition." During bulk changes, it seems that HelloID now may start more than 20 sessions at once, which can cause these errors. Just like the option on the Powershell target connector, it would be nice to have an option to limit the number of concurrent sessions on this connector as well.

I recently have users where not all the notification emails where send. I can find this in the audit log. And one of these emails contained the password. And notifications are the only official way to get the password of a new created user. So please add a option to resend notifications.

we would like to have a version history of all parts of HelloID provisioning that is restorable, like we had in IAM.

Instead of opening and adding an entitlement to 10, 20 or more BR's, we would like to be able to select multiple businessrules to add the selected entitlement to.

When reviewing suggested rules in the Rule Mining report, it is possible to filter the Entitlements list (for example on Redundant and/or Covered by configured rules) before clicking Create Rule. Currently, these filters are reset every time the user navigates to the next or previous suggested rule. As a result, the user has to reapply the same filters for every rule, and previously hidden entitlements become visible again. Expected behavior The selected entitlement filters should remain active while navigating between suggested rules until the user explicitly changes or clears the filters, or creates the rule. Why is this valuable? Keeping the filters applied makes reviewing consecutive suggested rules much more efficient and prevents users from repeatedly having to configure the same filters.