Action: Identify Consumer
This action specifies the kind of consumer identifier (IP address, HTTP authorization token, etc.) that CloudStreams will use to identify consumer applications. You can select only one identifier. Alternatively, this action provides an option to allow anonymous users to send requests, without restriction.
To set the Identify Consumer action parameters
1. In the CloudStreams Governance view, click the policy name.
2. In the policy editor on the right side of the page, double-click Identify Consumer in the Applied Actions list, and set the following action parameters.
Anonymous Usage Allowed
Specifies whether to allow anonymous users to send requests, without restriction.
IP Address
Right-click the action name and click Add IP Address to identify consumer applications based on their originating IP addresses.
Host Name
Right-click the action name and click Add Host Name to identify consumer applications based on a host name.
HTTP Token
Right-click the action name and click Add HTTP Token if you want to use HTTP Basic authentication to verify the consumer's authentication credentials contained in the request's Authorization header. CloudStreams authorizes the credentials against the list of users registered in the Integration Server on which CloudStreams is running. This type of consumer authentication is referred to as preemptive authentication. If you want to use preemptive authentication, you should also include the action Require HTTP Basic Authentication in the policy.
If you choose to omit Require HTTP Basic Authentication, the client will be presented with a security challenge. If the client successfully responds to the challenge, the user is authenticated. This type of consumer authentication is referred to as non-preemptive authentication.
Note:
If you select the value HTTP Token, do not include the Authorize Against Registered Consumers action in the policy. This is an invalid combination.
WSS Header Token
Right-click the action name and click Add WSS Header Token to validate user names and passwords that are transmitted in the SOAP message header in the WSS Username Token. If you select this option, you should also include the action Require WSS Username Token in the policy.
XPATH Token
Right-click the action name and click Add XPATH Token to validate consumer applications based on an XML element (represented by an XPATH expression you specify in the XPATH to Identify Token field).
Consumer Certificate
Right-click the action name and click Add Consumer Certificate to identify consumer applications based on information in a WSS X.509 certificate. If you select this option, you should also include the Require X.509 Token or the Require Signing action in the policy.
User ID
Right-click the action name and click Add User ID if you are applying the Identify Consumer action to a connector virtual service. You must select the User ID identifier; no other identifier is valid. User ID identifies consumer applications based on a list of users who are registered in the Integration Server on which CloudStreams is running. (You need to apply the Identify Consumer action to a connector virtual service if you apply the following actions to the connector virtual service: Monitor Service Level Agreement or Throttling Traffic Optimization (if you select its Limit Traffic for Applications option)).
Related Topics