1. Google Cloud Apigee Documentation
"Configuring TLS from Edge to the backend (Cloud and Private Cloud)": This document explicitly describes the process of mutual authentication. It states
"In two-way TLS
in addition to the server-side TLS authentication
the client also presents its certificate to the server for authentication... Two-way TLS is also called mutual TLS." This directly supports that both Apigee (as the client) and the target endpoint (the server) verify each other's identity.
2. Google Cloud Apigee Documentation
"About TLS/SSL": In the section "About two-way TLS/SSL
" the documentation clarifies the process: "For two-way TLS
the process is the same [as one-way TLS] except that the client also sends its certificate to the server for the server to verify." This confirms that the identity verification is mutual
involving both parties.