anchor.diff:  
   Some SAML Identity Providers will allow you to automatically import a metadata
   file when you configure the Elastic Stack as a Service Provider.
  +
  +You can optionally select to digitally sign the metadata file in order to
  +ensure its integrity and authenticity before sharing it with the Identity Provider.
  +The key used for signing the metadata file need not necessarily be the same as
  +the keys already used in the saml realm configuration for SAML message signing.
   
   [float]
   === Parameters
  
positive.code: `--service-name <name>`:: Specifies the value for the `<ServiceName>` element in
  the metadata. Defaults to `elasticsearch`.
  
  `--realm <name>`:: Specifies the name of the realm for which the metadata
  should be generated. This parameter is required if there is more than 1 `saml`
  realm in your {es} configuration.
  
negative.code: [--attribute <name>] [--service-name <name>]
  [--locale <name>] [--contacts]
  ([--organisation-name <name>] [--organisation-display-name <name>] [--organisation-url <url>])
  ([--signing-bundle <file_path>] | [--signing-cert <file_path>][--signing-key <file_path>])
  [--signing-key-password <password>]
  [-E <KeyValuePair>]
  [-h, --help] ([-s, --silent] | [-v, --verbose])
  --------------------------------------------------
  