Configure Single Sign-On (SSO)
- Last Updated: June 4, 2026
- 6 minute read
- MOVEit Automation
- Version 2026
- Documentation
Single Sign-On (SSO) is typically configured during the initial installation of MOVEit Automation. However, it can also be set up or modified after installation or following an upgrade, providing flexibility for administrators to adjust authentication settings as needed. Changes to SSO configuration, including enabling or modifying settings, are restricted to users with administrative privileges. Once SSO is configured, administrators can adjust the configuration as needed.
- Microsoft Entra ID (formerly Azure AD)
- Active Directory Federation Services (AD FS)
- Okta
Configuring SSO with Microsoft Entra ID
Prerequisites
Ensure you have access to your organization's pre-configured Entra portal and the MOVEit Automation server. You must have administrative rights to complete the setup.
Required values and token configuration
- Client ID: is a unique identifier assigned to your application when you register it with the identity provider, located in the app registration overview.
- Tenant (Directory) ID: is a unique identifier assigned to your organization’s instance. It is used to identify your tenant across cloud services like Microsoft 365, Azure, and MOVEit when integrating with SSO. It is located in the app registration overview.
- Issuer URL: is a unique
identifier for the identity provider and is used by clients to validate
tokens. For example, the format for a Microsoft Entra ID Issuer URL
is:
https://login.microsoftonline.com/tenant_id/v2.0 - Redirect URI: The URI to which the identity provider will send authentication
responses. This value must be registered in the Entra App Registration
as a single‑page application (SPA) Redirect URI and must exactly match
the Redirect URI configured MOVEit Automation.For MOVEit Automation, the Redirect URI typically takes the form:
Where your-moveit-server is the MOVEit Automation Web Admin server address.https://your-moveit-server
Token configuration
- In the App Registration, go to Token Configuration.
- Click Add group
claim.
- In the Edit groups
claim panel:
- Select ID.
- Choose
NetBIOSDomain\sAMAccountNameas the format.
- Click Save.
- In the Edit groups
claim panel:
- Click Add optional
claim.
- Choose Token Type: ID.
- Select the following claim:
onprem_sid
- To save the changes, click Add.
To enable SSO in MOVEit Automation, two registry values must be configured on the MOVEit Automation server: HKEY_LOCAL_MACHINE\Software\Standard Networks\MOVEitCentral
- Open the Windows Registry Editor.
- Navigate to the MOVEit Automation registry settings: HKEY_LOCAL_MACHINE\Software\Standard Networks\MOVEitCentral.
- Add the Web Admin Auth Server URL:
- Right-click in the right pane and select .
- Enter
WebAdminAuthServerUrl. - Double-click the new entry and enter the URL of your MOVEit Web Admin interface (for example, https://your-moveit-server.com).
- Add the Ignore Certificate Errors Flag. This is only
necessary when using a self-signed certificate, which is the default
configuration in MOVEit Automation. Self-signed
certificates can trigger validation errors. Setting this flag to
trueallows the system to bypass those errors. This configuration is not required when using a certificate issued by a trusted Certificate Authority..- Right-click in the right pane and select .
- Enter
WebAdminAuthIgnoreCertErrors. - Double-click the new entry and set the Value data to 1 (which means true).
- Restart the MOVEit Automation services to apply the settings
The config.properties file is in the HOME\MOVEit\MOVEit Automation Web Admin\Tomcat\webapps\ROOT\WEB-INF\classes\ directory. Where HOME is the MOVEit Automation directory that is created during installation.
- Open the config.properties file in a text editor As Administrator.
- Edit the following properties:
Table 1. Property
Description
Values
security.auth.grant-enabled.token-exchange=Enables SSO, allowing MOVEit to exchange an external token for an internal session.
True or False
security.auth.grant-enabled.password=Enables password access, allowing traditional username/password log on.
True or False
security.auth.hide-ui-password-login=Controls whether the password login option is visible in the UI. If set to
true, users will only see the SSO login option.True or False
For more information about the logon options, see SSO log on options.
security.auth.groups-claim-name=Specifies the claim name in the token that contains the user's group memberships. MOVEit uses this to assign roles or permissions.
For example, groups
security.auth.username-claim-name=Defines the claim that MOVEit should use as the username. This is how the user is identified in MOVEit.
For example, preferred_username
security.auth.sid-claim-name=Specifies the claim that contains the SID (Security Identifier), often used for mapping to on-prem AD. users
For example,
onprem_sidsecurity.auth.oidcClientId=The Client ID registered in your identity provider. MOVEit uses this to identify itself during authentication.
For example,
12345678-90ab-cdef-1234-567890abcdefsecurity.auth.oidcIssuerURL=The Issuer URL of your identity provider. This tells MOVEit where to validate tokens.
For example, https://login.microsoftonline.com/tenant_id/v2.0
- To save the config.properties file, close the file and restart MOVEit Automation Web Admin service in Services.
Configuring SSO with AD FS
Prerequisites
Ensure you have access to your organization's AD FS server and the MOVEit Automation server. You must have administrative rights to complete the setup.
Create an Application Group in AD FS
- Open the AD FS Management Console.
- Click :
- Enter a name for the application group.
- Select Web browser accessing a web application.
- The Client identified field auto-populates the Client ID.
- Add the Redirect URI. This is the MOVEit Automation Web Admin URL.
- Choose access control policy settings based on you organization's requirements and complete the Wizard steps.
Configure Claim Rules
- In the the AD FS Management Console, select Application Groups and select the group from the list.
- Right-click the group to open the properties. Click group-name-Web Application.
- Select the .
- Select Send LDAP Attributes as Claims.
- Name the claim. Take note of this value as it is required in the config properties.
- Select Active Directory from the Attribute store drop-down list.
- Select the LDAP Attribute Token Groups Qualified by Domain Name from the drop-down list.
- Finish and apply the rule.
Update the MOVEit Automation Configuration
The config.properties file is in the HOME\MOVEit\MOVEit Automation Web Admin\Tomcat\webapps\ROOT\WEB-INF\classes\ directory. Where HOME is the MOVEit Automation directory that is created during installation.
- Open the config.properties file in a text editor As Administrator.
- Edit the following properties:
Property
Description
Values
security.auth.grantenabled.token-exchange=Enables SSO, allowing MOVEit to exchange an external token for an internal session.
True or False
security.auth.grantenabled.password=Enables password access, allowing traditional username/password log on.
True or False
security.auth.hide-uipassword-login=Controls whether the password login option is visible in the UI. If set to
true, users will only see the SSO login option.True or False
security.auth.groups-claim-name=Specifies the claim name, as defined during the creation of the claim rules.
For example, groups
security.auth.username-claim-name=Defines the claim that MOVEit should use as the username. This is how the user is identified in MOVEit.
Typically
upnfor AD FSsecurity.auth.sid-claimname=The claim for SID.
Typically
sidfor AD FSsecurity.auth.oidcClientId=The Client ID from AD FS application group.
For example,
12345678-90ab-cdef-1234-567890abcdefsecurity.auth.oidcIssuerURL=The Issuer URL of your AD FS server.
For example, https://your-adfs-server/adfs
- To save the config.properties file, close the file and restart MOVEit Automation Web Admin service in Services.
Configuring SSO with Okta
Prerequisites
- You have an Okta tenant with administrative access.
- Okta is integrated with Active Directory or Microsoft Entra ID and is successfully synchronizing.
- You have administrative access to the MOVEit Automation server.
- MOVEit Automation Web Admin is installed and accessible.
Create an OIDC Application in Okta
As an Okta administrator, create an application integration for MOVEit Automation:
- Go to and select Create App Integration.
- Choose OIDC – OpenID Connect and select Single‑Page Application.
- Configure the application with the following settings:
- Grant type: Authorization Code
- Sign‑in redirect URIs: Add the MOVEit Automation Web Admin URL(s).
- Assignments: Grant access to the appropriate users or groups and disable Federation Broker Mode.
- Save the application and note the Client ID, which is required later.
Configure SID Mapping in Okta
MOVEit Automation requires the Active Directory SID for an SSO login user to be included in the ID token.
- Go to and select the Okta User profile.
- Add a new attribute with the following values:
- Name:
onprem_sid - Data type: String
- User permission: Read Only
- Name:
- Save the attribute.
- In Profile Editor, select the Active Directory User profile.
- Open Mappings.
- Map the Active Directory attribute
objectSidto the Okta user attributeonprem_sid. - Save the mapping.
Add the SID Claim to the OIDC Token
- Go to .
- Select the default authorization server.
- Open the Claims tab and add a new claim with the
following values:
- Name:
onprem_sid - Include in token type: ID Token
- Value type: Expression
- Value:
user.onprem_sid - Include in:
openid
- Name:
- Save the claim.
- Use the Token Preview feature to verify that the
onprem_sidvalue appears in the ID token for an Active Directory user.
- Go to .
- Open the default identity provider.
- In Access Policies, add a new policy and rule. Leave the rule settings to their default.
Update the MOVEit Automation Configuration
The config.properties file is in the HOME\MOVEit\MOVEit Automation Web Admin\Tomcat\webapps\ROOT\WEB-INF\classes\ directory. Where HOME is the MOVEit Automation directory that is created during installation.
- Open the config.properties file in a text editor As Administrator.
- Edit the following properties:
Property
Description
Values
security.auth.grantenabled.token-exchange=Enables SSO, allowing MOVEit to exchange an external token for an internal session.
For Okta SSO, set this to True
True or False
For Okta SSO, set this to True
security.auth.grantenabled.password=Enables password access, allowing traditional username/password log on.
This can be enabled alongside SSO.
True or False
security.auth.hide-ui-password-login=(Optional) Controls whether the password login option is visible in the UI. If set to
true, users will only see the SSO login option.True or False
security.auth.groups-claim-name=Specifies the groups claim name, as defined during the creation of the claim rules.
Value defined in Okta. For example,
groupssecurity.auth.username-claim-name=Defines the claim that MOVEit should use as the username. This is how the user is identified in MOVEit.
Value defined in Okta. For example, preferred_username
security.auth.sid-claim-name=The claim for SID.
Value defined in Okta. For example,
onprem_sidsecurity.auth.oidc-client-id=The Client ID from the Okta application.
Defined in Okta. For example,
12345678-90ab-cdef-1234-567890abcdefsecurity.auth.oidc-issuer-url=Okta issuer URL.
Defined in Okta. For example, https://your-org.okta.com/oauth2/default
- To save the config.properties file, close the file and restart MOVEit Automation Web Admin service in Services.
Once complete, users can sign in to MOVEit Automation Web Admin using Okta-based SSO.