Integrations
MyPass integrates with the directory services, ERP platforms, mainframes, ITSM tools, and MFA providers your organisation already runs — through a single secure MyPass Gateway. No rip and replace. Supports 95+ target systems simultaneously.
Directory & Identity
MyPass is built around Active Directory as its primary identity source, with full support for Entra ID (Azure AD), LDAP, and cloud directories.
On-Premise
Full SSPR, IVM, Password Sync, and Password Filter support. Domain controller interceptor captures password change events before encryption. Supports all AD versions 2012–2022. Multiple domain and forest configurations supported.
Integration Guide ↗Cloud / Hybrid
Cloud-native integration for hybrid and cloud-first environments. Supports SSPR and sync for hybrid AD setups. Entra ID can be configured as primary source or secondary target alongside on-premise AD.
Integration Guide ↗Productivity
Reset and sync Google Workspace credentials alongside AD in a single SSPR flow. No separate admin intervention required. Useful for organisations running hybrid Microsoft/Google environments.
Microsoft
Synchronise on-premise AD password changes to M365 accounts automatically, eliminating the common support call caused by AD/cloud credential divergence in hybrid environments.
SAP
SAP environments are complex — multiple systems, multiple clients, ABAP and Java stacks side by side. MyPass handles the full SAP landscape with two complementary approaches.
Method 1
MyPass detects Windows / Active Directory password changes via the domain controller interceptor and instantly propagates that new password to all linked SAP systems. Users get a seamless single-password experience without touching SAP at all. Supports ABAP and Java/UME stacks. SNC (Secure Network Communications) supported for encrypted connectivity.
Best for: environments where SSO isn't deployed and users should maintain one Windows credential across all SAP systems.
Method 2
Users request SAP password resets through the MyPass SSPR portal, secured with MFA. Preferred when security separation between Windows and SAP credentials is required. Average reset time under one minute. Unlocks accounts locked by failed login attempts simultaneously.
Best for: organisations that want separate SAP and AD credential policies, or privileged SAP accounts that should not mirror Windows passwords.
Technical requirements: One service account per SAP instance with sufficient rights. ABAP systems require ABAP function module installation. Java/UME systems use SPML protocol. Multi-client environments (e.g. Client 100 vs 300) handled natively. Selective sync scope lets you isolate dev, UAT, and production SAP systems independently.
SAP Integration Guide ↗ERP & Mainframe
The systems SSO can't reach. MyPass Password Sync and SSPR connect to the full legacy estate — Oracle, IBM mainframe, iSeries — through the MyPass Gateway.
Oracle
Password reset and sync for Oracle EBS application user accounts and database logins. Supports Oracle 11g through 19c. Bidirectional sync available — Oracle changes can trigger AD updates where required.
IBM
Native z/OS mainframe integration via the MyPass Gateway. RACF, ACF2, and Top Secret security managers supported. Password reset, sync, and account unlock. No mainframe-side code changes required.
Integration Guide ↗IBM
IBM i profile database password sync and reset. Works alongside existing AS/400 security policy without modification. Real-time on AD change event via Gateway connector.
Integration Guide ↗Unix / Linux
Local PAM account sync across Linux, AIX, and Unix servers. Eliminates the last local password island from the estate. Triggered on AD change event — no user action or scheduled job required.
Integration Guide ↗Database
Database login credential sync alongside application accounts. Removes static passwords from service accounts. SQL Server 2016+ and MySQL 5.7+ supported.
Integration Guide ↗Collaboration
Lotus Notes / Domino environments still in production. Password Sync keeps Domino credentials aligned with AD without manual admin involvement.
ITSM Platforms
IVM integrates bidirectionally with your ITSM platform. The ITSM system triggers verification automatically when a ticket is opened. MyPass completes verification and writes results back — closing the ticket loop without agent intervention.
Certified
ServiceNow Store certified. IVM verification panel embedded directly in incident and service request forms. Automatic ticket update and closure on verification completion. Supports ServiceNow Tokyo, Utah, Vancouver, and Washington releases.
Supported
IVM verification widget embedded in the Zendesk agent interface. Supports Zendesk Support and Zendesk Suite. Ticket enriched with verification result via Zendesk API on completion.
Supported
IVM panel within the Jira Service Management agent queue. Works with Jira Cloud and Jira Data Centre editions. Verification results written back to the Jira ticket automatically.
Supported
Deep integration including automatic ticket enrichment and IVM verification panel. Compatible with ManageEngine ServiceDesk Plus Cloud and On-Premises editions.
Supported
Integration via Ivanti's standard REST API. Supports Ivanti Neurons for ITSM and Ivanti Service Manager. Bidirectional ticket enrichment on verification completion.
Supported
IVM integration via HaloITSM REST API. Verification triggered on ticket type, results posted back automatically. Contact us for specific configuration details.
Supported
IVM integration via TOPdesk API. Supports TOPdesk SaaS and on-premise deployments. Verification results and audit trail written back to the TOPdesk call card.
Authentication Providers
MyPass integrates with your existing MFA platform for both self-service resets and live helpdesk verification. Users already enrolled in Okta, Duo, or RSA can use those same credentials — no re-enrolment required.
MyPass Gateway
The MyPass Gateway is a lightweight on-premise component that acts as the integration bridge between the MyPass Cloud tenant and your internal systems. The cloud tenant initiates an inbound TLS connection to the Gateway — secured by inbound NAT and application-layer security — and the Gateway traverses from there to your on-premise targets. No VPN required.
Deploy one Gateway per environment, or multiple Gateways per region for geographically distributed estates. Each Gateway handles local system updates independently — isolated networks, remote datacentres, and disconnected segments all supported.