Administering Mediator : The Built-In Run-Time Actions : The Built-In Run-Time Actions for Virtual Services : Additional Actions
Additional Actions
Mediator provides the following actions, which you can use in conjunction with the actions.
*Identify Consumer: You use this action in conjunction with an authentication action (Require WSS Username Token, Require WSS X.509 Token, or Require HTTP Basic Authentication). Alternatively, this action can be used alone to identify consumers only by host name or IP address.
*Require HTTP Basic Authentication: This action uses HTTP basic authentication to verify the consumer's authentication credentials contained in the request's Authorization header against the Integration Server's user account.
Note:  
Mediator also supports NTLM and OAuth2 authentication, which you can specify in a virtual service's Routing Protocol step. For details, see CentraSite User’s Guide.
*Authorize User: This action authorizes consumers against a list of users and a list of groups registered in the Integration Server on which Mediator is running. You use this action in conjunction with an authentication action (Require WSS Username Token, Require WSS SAML Token, or Require HTTP Basic Authentication).
*Authorize Against Registered Consumers: This action authorizes consumer applications against all Application assets that are registered in CentraSite as consumers for the service.
*Log Invocations: This action logs request or response payloads to a destination you specify.
*Validate Schema: This action validates all XML request and response messages against an XML schema referenced in the WSDL.
For complete details of all actions, as well as common usage cases for identifying or authenticating consumers, see CentraSite User’s Guide.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback