The Bastion secures your applications with AAPM

The WALLIX Bastion offers AAPM (application-to-application password management) with a fingerprinting proprietary technology to authenticate third-party applications.

application-to-application-password-management-aapm.jpeg

What is AAPM?

But what is application-to-application password management? Several applications of your IT infrastructure require to connect to other applications to process theirs services. As for users that have to authenticate to a server to access its services, those applications have also to authenticate to those servers.

A well-known problem is to allow a server, for example a ticketing server such as Redmine, to authenticate with a directory service (AD). Once the Redmine server is authenticated, it can validate the identity of users wishing to access its services by using the AD connection. This way, AD accounts are not duplicated and the overall authentication of your users is centralized.

The problem AAPM solves

Today, credentials used from an application to connect to another application are stored within a flat configuration file, most of the time, in scripts and unencrypted. The purpose of AAPM is to eliminate these kind of files as well as any hard-coded password that might otherwise exist in applications and unsecure DevOps processes, and to provide a secured mechanism to authenticate an application with another application – no exposed passwords necessary.

The WALLIX Bastion offers AAPM with a fingerprinting proprietary technology to authenticate third-party applications with each other for secure DevOps.