delete_allowed_db_by_entry_id

This command removes a User-DB association by the user's ID.

You can find the ID by using the list_allowed_db_by_user API.

Note: To apply the changes to the active User-DB association map, run update_user_db after you run this command.

This API is available in Guardium V9.5 and later.

REST API syntax

This API is available as a REST service with the DELETE method. Call this API as follows: 
DELETE https://[Guardium hostname or IP address]:8443/restAPI/allowed_db

GuardAPI syntax

delete_allowed_db_by_entry_id parameter=value

Parameters

Parameter Value type Description
id Long Required. The record ID of the User-DB association.
api_target_host String

Specifies the target hosts where the API executes. Valid values:
  • all_managed: execute on all managed units but not the central manager
  • all: execute on all managed units and the central manager
  • group:<group name>: execute on all managed units identified by <group name>
  • host name or IP address of a managed unit: specified from the central manager to execute on a managed unit.  For example, api_target_host=10.0.1.123.
  • host name or IP address of the central manager: specified from a managed unit to execute on the central manager. For example, api_target_host=10.0.1.123.

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.

GuardAPI example

grdapi delete_allowed_db_by_entry_id id=2

Sample output

ID=0
Number of matches: 1
When complete, in order for synchronization to take effect, run update_user_db
ok