Modifying an HTTP receiver for metadata streaming using the CLI

Prev Next

Follow these steps to change settings on an HTTP receiver for metadata streaming of Email Security - Server appliance email events:

To modify an existing HTTP metadata receiver using the CLI:
  1. Go to CLI configuration mode.

    hostname > enable
    hostname # configure terminal
  2. Update the IPv4 address or hostname of the HTTP server to send metadata streaming events to:

    hostname (config) # datastreaming configuration protocol http consumers <service-name> server-url <url>

    Note

    IPv6 addresses are not supported.

  3. Change the authentication method: token or basic.

    hostname (config) # datastreaming configuration protocol http consumers <service-name> auth method {TOKEN | BASIC}
  4. Change the authentication token.

    hostname (config) # datastreaming configuration protocol http consumers <service-name> auth token <token>
  5. Change the user name if you are using a basic authentication method.

    hostname (config) # datastreaming configuration protocol http consumers <service-name> auth username <username>
  6. Change the password if you are using a basic authentication method.

    hostname (config) # datastreaming configuration protocol http consumers <service-name> auth password <password>
  7. Change the content type that is to be streamed to the HTTP receiver.

    hostname (config) # datastreaming configuration protocol http consumers <service-name> content-type {application/json | application/x-www-form-urlencoded | text/plain}
  8. Change the minimum version of the TLS protocol to secure metadata streaming on the HTTP receiver.

    hostname (config) # datastreaming configuration protocol http consumers <service-name>  ssl min-version {TLSv1 | TLSv1.1 | TLSv1.2}
  9. Verify the changes.

    hostname (config) # show datastreaming configuration
    
    data-streaming configuration:
       Feature enabled                  :    yes
       HTTP enabled                     :    yes
       Rsyslog enabled                  :    yes
    
       Helix Configuration:
       Helix enabled                    :    no
       Helix FQDN                       :
       Helix bootstrap certificate      :
    
       Subscribed http consumers        :    1
    
       Subscriber 01 of type: http:
       name                     =    HTTP_Receiver_Milpitas
       enable                   =    yes
       server-url               =    
    https://milpitas.fireeye.com:8443/receiver.jsp
       content-type             =    text/plain
       collector-type           =    ********
       Authorization:
       auth enable              =    yes
       method                   =    TOKEN
       token                    =    xxxxxxxxxxxxxxxxxxxxxxxx
       username                 =    
       auth password            =    
       SSL:
       verify                   =    yes
       min version              =    TLSv1
       ssl supplemental CA list =    none
       TLS                      =    yes  
       hostname (config) #
      
  10. Save the changes to the current active configuration.

    hostname (config) # write memory