How Does Mediator Identify Consumer Applications at Run Time?

To determine the consumer application from which a request was submitted, a virtual service must have a run-time policy that includes an Evaluate * action. This action extracts a specified identifier from an incoming request and locates the application asset defined by that identifier.

For example, if you configure the Evaluate IP Address action to identify consumers by IP address, Mediator extracts the IP address from a request's HTTP header and searches its list of application assets for the application that is defined by that IP address.

Identifier	Description
IP Address	The IP address from which the request originated.
Host Name	The name of the host machine from which the request originated.
HTTP Authentication Token	The user ID submitted by the requestor when it was asked to provide basic HTTP credentials (user name and password).
WS-Security Authentication Token	The WSS username token supplied in the header of the SOAP request that the consumer application submitted to the virtual service.
Consumer Certificate	The X.509 certificate supplied in the header of the SOAP request that the consumer application submitted to the virtual service.
XPath Expression	The custom token supplied using an XPath expression in the header of the request that the consumer application submitted to the virtual service.
Kerberos Authentication Token	The OAuth2 credentials supplied in the header of the SOAP request that the consumer application submitted to the virtual service.
OAuth2 Authentication Token	The Kerberos token supplied in the header of the SOAP request that the consumer application submitted to the virtual service.