This command helps maintain the mapping between database users (that is, invokers of SQLthat causes a violation) and email addresses for real-time alerts.
- serverIp: You can use the percent sign (%) as a wildcard instead of the
character for any element in the IP address. For example, the following addresses are valid:
However, the following example is not valid: 192.%
- serverIp: You can use the percent sign (%) as a wildcard instead of the character for any element in the IP address. For example, the following addresses are valid:
- serviceName: Wildcards (%) are allowed.
- dbUserName: Wildcards are not valid. The % sign is not a special character.
- emailAddress: Wildcards are not valid. The % sign is not a special character.
This API is available in Guardium V9.5 and later.
REST API syntax
POSTmethod. Call this API as follows:
POST https://[Guardium hostname or IP address]:8443/restAPI/db_user_mapping
|dbUserName||String||Required. The DB username.|
|emailAddress||String||Required. For real-time alerts, the email address that maps to the DB user. The at symbol (@ ) is required.|
|serverIp||String||Required. The server IP address.|
|serviceName||String||Required. The server name.|
Specifies the target hosts where the API executes. Valid values:
IP addresses must conform to the IP mode of your network. For dual IP mode, use the same IP protocol with which the managed unit is registered with the central manager. For example, if the registration uses IPv6, specify an IPv6 address. The hostname is independent of IP mode and can be used with any mode.
grdapi create_db_user_mapping serverIp=192.168.1.% serviceName=ora1 dbUserName=hadrian emailAddressfirstname.lastname@example.org