CentraSite 10.7 | CentraSite User’s Guide | Runtime Governance | Consumer Management | Run-Time Consumer Registration Scenarios
 
Run-Time Consumer Registration Scenarios
 
Scenario A: Virtual Service without API Consumption Settings and Evaluate Policy Actions
Scenario B: Virtual Service without API Consumption Settings and with Evaluate Policy Actions
Scenario C: Virtual Service with API Consumption Settings and without Evaluate Policy Action
Scenario D: Virtual Service with API Consumption Settings and Evaluate Policy Action
Note:
This section is not applicable if the CentraSite run-time aspects are not enabled. By default, run-time aspects configured from CentraSite are disabled. However, you can enable them if required. To enable the CentraSite run-time aspects, see Enabling CentraSite Run-Time Aspects.
Pre-requisite:
To impose an approval process for consumer registration process, ensure that you have created the required Consumer Registration design-time policy.
At run-time, you might want to register as consumer an asset instance of a virtual type, for example, an asset of Virtual Service type, in which case you would have to specify the authentication settings or consumer identifiers or both, and would invoke the asset to query and obtain the data. This would help to indicate the run-time asset usage.
An API provider (owner of the API) specifies the type of authentication (API key or OAuth2 token using the consumption settings) and configures a set of Evaluate * actions (using the run-time policies) to identify and authorize the consumer that request the consumption access to the metadata of the particular API. Based on the specified enforcement definitions for the API, CentraSite offers interactive user interfaces for the following four exemplary scenarios:
Is API Consumption Settings Configured?
Is an Evaluate Action Configured?
For Procedures…
No
No
No
Yes
Yes
No
Yes
Yes