Securing

Know how data stays secure with SSO and OAuth 2.0 for access, strong ciphers for protection, and masking for privacy.

Defining allowed IP addresses
webMethods Integration connects easily with most third-party services. To reach servers behind a firewall, webMethods Integration uses specific IP addresses. webMethods Integration uses a set of static IP addresses that you allow in your firewall. It helps to connect to your servers to run integrations, use SSH, or access services like MySQL. Learn about the set of static IP addresses that you must allow in your firewall.
Setting up OAuth 2.0
Learn how to protect integration services and REST APIs by using the OAuth 2.0 protocol.
Understanding cipher suites
Know the supported cipher suites for inbound traffic under both TLS 1.3 and TLS 1.2. When you create a Transport Layer Security (TLS) context, you can specify the list of cipher suites that can be used. If you do not specify any cipher suites, the default cipher suites for the selected TLS version are used.
Understanding keystores, truststores, and certificates
Keystores and truststores are secure files that store keys and certificates that are used for SSL authentication, encryption, decryption, and digital signing and verification. Learn how to work with keystores, truststores, and certificates in webMethods Integration.
Setting up secure connections with Mutual TLS (mTLS)
Masking data
Add a layer of security to your application data by masking action input and output data.