Users register information with Activate to enable validation and verification of the user during a Password Reset request. 

The users answers are encrypted when stored in the Activate database. AES 256bit encryption is used and the answer is seeded with information from the user account. Therefore the same answer for different users does not generate the same encrypted value.

A random 256bit encryption key is generated for each server installation the first time it is requested. The encryption key is stored in //Resources/Configuration/EncryptionKey. 

WARNING: If this value is changed then ALL encrypted information on the server will be lost and not be accessible.

The stored answers are stored in reversible encryption hash to enable the ability for the service desk to use this information to manually verify the user. This is an optional facility that can be turned off by not utilising and publishing the task in Activate.

The users answers are not decrypted for any other operation. All other operations (including checking the users answers during a Reset Request) the password hash is checked and not the plain text answer.

Activate encrypted information can only be decrypted by 'Trusted Accounts'. By default, the only Trusted Accounts are the Activate Job Service account and the Activate Web Portal Application Pool Account (if different). Trusted Accounts are configured at //Resources/Configuration/Trusted Account. An other user that attempts to decrypt a value in Activate will get a blank result.

The users answers and password are also encrypted and secured during communication with the Activate Password Reset web service. This web service is used by the Activate External Web Portal and Activate Windows Plugin. The Activate Web Portal is not encrypted unless SSL is installed and used. The Activate web portal never asks for a users final password, and the other information transmitted is the users answers.

The encryption key for data transferred between the clients and password reset web service has a default value that is hard-coded into the clients and web service. This encryption key can be changed, however, all clients and servers must have the same key or communication will be lost. Details on this are in the Activate Windows Client installation guide.  

Note: Changing this value is not recommended.

Minimum AD Permissions Required for the Password Manager Module

Activate Password Module Encryption

Microsoft’s cloud platform providing infrastructure, networking, storage, and application services. In Activate, it’s used as the hosting environment or for integration with Microsoft 365 and Entra ID services.

Azure

DotNetVersion

Microsoft Entra Connect (formerly Azure AD Connect) is a tool that syncs on-premises Active Directory identities with Microsoft Entra ID, enabling hybrid identity and seamless access to cloud resources.

Microsoft_Entra_Connect

Active Directory (AD) is Microsoft’s directory service that stores and manages user accounts, devices, and permissions, enabling secure authentication and centralized access control within a Windows network.

Active_Directory

ActivateJobService

ActivateAdministrator

SupportedPowerShellVersions

SupportedOSVersions

SupportedSQLVersions

Name that identifies the instance of Activate.  This is only used by Administrators and isn't displayed to end users.

instance_name

An installation type of Activate where there is no local domain connection, all authentication, authorisation and identity management is handled by Entra ID.

Cloud_Only

Microsoft Entra ID (formerly Azure Active Directory) is Microsoft’s cloud-based identity and access management service, providing secure authentication, user lifecycle management, and access control for Microsoft 365 and other apps.

Microsoft_Entra_ID

A software switch that enables or disables functionality at runtime without redeploying code. In Activate, they are configured under //Resources/Configuration/FeatureFlags.

feature_flag

Microsoft module for managing Exchange Online, using modern authentication and REST API–based cmdlets for faster, more reliable automation of mailboxes, compliance, and organisation settings.

EXO_V3_PowerShell_Module

An Organizational Unit (OU) is a container in Active Directory used to organise users, groups, computers, and other objects within a domain. OUs help structure resources logically and apply group policies for easier management and administration.

A User Type is a template in Activate that defines rules, attributes, and behaviours for a category of users (e.g., Employee, Contractor), ensuring consistent user account setup and configuration.

User_Type

A resource object in Activate representing a physical or virtual Exchange Server

Exchange_Server_Resource

Defines the object type that the resource will emulate or operate as.

Class_parameter

Clonesthe selected inherited parameter to make a local copy to override the value

Override

Runs the Activate Provisioning Server and performs actions across target systems.

Orchestrator_Account

A complete, immutable log of identity-related events, including provisioning actions, access approvals, and policy evaluations.

Audit_Trail

An integration module that enables Activate to read/write data from external systems (e.g., provisioning accounts in Azure AD).

Connector

A periodic process where managers or data owners validate that users still require their existing access — critical for compliance.

Access_Certification_and_Review

A user-initiated process to gain access to new systems or roles, often requiring manager or system owner approval.

Access_Request

Any downstream application or service where identities need access (e.g., Active Directory, Okta, Salesforce).

Target_System

The authoritative system from which identity data is imported (e.g., HRIS like Workday or SAP SuccessFactors).

Identity_Source

An access control model that uses user, resource, or environment attributes (e.g., department = "HR", location = "US") to make access decisions dynamically.

ABAC_Attribute-Based_Access_Control

An access control model where users receive permissions based on assigned roles. This model helps enforce least privilege.

RBAC_Role-Based_Access_Control

A collection of entitlements assigned based on a user’s job function or department. Roles simplify access management and are often tied to policies (e.g., "Finance Analyst Role").

Role

A specific access right or permission within a system (e.g., "Read-only access to Salesforce Reports"). Entitlements can be grouped into roles.

Entitlement

The removal or disabling of user accounts and access when they are no longer required — for example, when an employee leaves the organization.

Deprovisioning

The automated process of creating accounts and granting access to systems or applications based on a user’s role or attributes.

Provisioning

A digital representation of a user (employee, contractor, service account, etc.) within an organization. Each identity is typically linked to a unique identifier, such as an email address or employee ID.

Identity

This is the process of bringing on a new user

Onboarding

Hierarchical Role-Based Provisioning automates user access by assigning roles based on organisational structure, ensuring users inherit the correct permissions and resources aligned to their position or function.

Hierarchical_Role-Based_Provisioning

A group email address that automatically forwards messages to all its members, allowing you to send emails to multiple recipients at once.

Distribution_List

An expression is a conditional statement using Activate expression syntax.

expression

AzureProductName

Active Directory Permissions for Password Reset Only

Activate Knowledge Centre

For Engineers

For Architects

For Service Desk

For C-Suite and Decision Makers

For Partners & Analysts

Welcome to Activate Knowledge Centre

What is Activate?

Key terms

System Overview

Solution Architecture Overview

Overview

Key Components

Deployment Models

Security Architecture Overview

Azure/EntraID and Activate

Workflow Designer

Platform Governance and Operations

Core Architecture

System Requirements