Note: | Beginning with version 9.9, CentraSite does not support registering Application assets as consumers of an asset using the Control UI. This means that there is no consumer registration procedure in Control UI. As a result: ![]() ![]() ![]() Therefore, you cannot register Application assets as consumers of an asset using the CentraSite Control UI. Instead, you can use the enhanced interface of CentraSite Business UI which supports consumer registration for users, groups, Application and arbitrary assets (in contrast, earlier versions of CentraSite Business UI supported a standardized interface for consumer registration of Application assets only). Documentation of the prior consumer registration interface is available to CentraSite customers who have a current maintenance contract in Empower Product Support website. To register Application assets as consumers of an API using the Business user interface, you perform the following high-level steps: 1. Include the Evaluate (consumer) action in the API's run-time policy. To identify the consumer applications that are requesting an API, that asset must have a run-time message flow that includes one or more Evaluate * actions. In these actions, you specify the consumer identifier(s) you want to use for identifying consumer applications. (Alternatively, you may configure these actions to allow unrestricted access.) These actions extract the specified identifier from an incoming request and locate the consumer application defined by that identifier. For example, if you configure the Evaluate IP Address action to identify consumers by a specific IP address, the PEP extracts the IP address from a request’s HTTP header at run time and searches its list of Application assets for the application that is defined by that specified IP address. You can configure the Evaluate * actions to identify consumer applications based on one or more of the following consumer identifiers in a request message:
When deciding which Evaluate * action to use to identify and authenticate a consumer application, consider the following points: ![]() ![]() ![]() For information about the Evaluate * actions, see Built-In Run-Time Actions Reference for
APIs. 2. Create an Application asset in the registry. In the Application asset you specify precise values for the consumer identifier(s) that you specified in the Evaluate * actions. For details, see The Identification Profile. 3. Specify the Application asset in the Consume Asset dialog of the API you want to consume. Use the Consume action in the details page of the API you want to consume. This opens the Consume Asset dialog. For procedures, see Implementing Consumer Registration The run-time behavior of identifying and authenticating consumers is as follows: 1. CentraSite translates the Application asset to the appropriate WS-Security policy actions or an equivalent XML when the Application asset is enforced by the PEP. 2. When a consumer application requests access to an API, the PEP tries to map the consumer's identifier (which is found in the request) to an identifier in the Application asset. ![]() ![]() 3. The identified or authenticated consumer information is published back to the registry as part of the transaction or other events. This information is used to correlate the consumer-specific run-time dependencies. |