Skip to content

Commit

Permalink
[DOCS] Improve connector privateKey and certificateAuthoritiesData se…
Browse files Browse the repository at this point in the history
…tting examples (#190932)
  • Loading branch information
lcawl authored Aug 21, 2024
1 parent be2f7f4 commit 385281b
Show file tree
Hide file tree
Showing 2 changed files with 26 additions and 10 deletions.
27 changes: 21 additions & 6 deletions docs/management/connectors/pre-configured-connectors.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -513,14 +513,19 @@ xpack.actions.preconfigured:
jwtKeyId: fedcbazyxwvutsrqponmlkjihgfedcba <4>
secrets:
clientSecret: secretsecret <5>
privateKey: -----BEGIN RSA PRIVATE KEY-----\nprivatekeyhere\n-----END RSA PRIVATE KEY----- <6>
privateKey: | <6>
-----BEGIN RSA PRIVATE KEY-----
MIIE...
KAgD...
... multiple lines of key data ...
-----END RSA PRIVATE KEY-----
--
<1> Specifies whether the connector uses basic or OAuth authentication.
<2> The user identifier.
<3> The client identifier assigned to your OAuth application.
<4> The key identifier assigned to the JWT verifier map of your OAuth application.
<5> The client secret assigned to your OAuth application.
<6> The RSA private key. If it has a password, you must also provide `privateKeyPassword`.
<6> The RSA private key in multiline format. If it has a password, you must also provide `privateKeyPassword`.

[float]
[[preconfigured-servicenow-configuration]]
Expand Down Expand Up @@ -563,14 +568,19 @@ xpack.actions.preconfigured:
jwtKeyId: fedcbazyxwvutsrqponmlkjihgfedcba <4>
secrets:
clientSecret: secretsecret <5>
privateKey: -----BEGIN RSA PRIVATE KEY-----\nprivatekeyhere\n-----END RSA PRIVATE KEY----- <6>
privateKey: | <6>
-----BEGIN RSA PRIVATE KEY-----
MIIE...
KAgD...
... multiple lines of key data ...
-----END RSA PRIVATE KEY-----
--
<1> Specifies whether the connector uses basic or OAuth authentication.
<2> The user identifier.
<3> The client identifier assigned to your OAuth application.
<4> The key ID assigned to the JWT verifier map of your OAuth application.
<5> The client secret assigned to the OAuth application.
<6> The RSA private key. If it has a password, you must also provide `privateKeyPassword`.
<6> The RSA private key in multiline format. If it has a password, you must also provide `privateKeyPassword`.

[float]
[[preconfigured-servicenow-sir-configuration]]
Expand Down Expand Up @@ -613,14 +623,19 @@ xpack.actions.preconfigured:
jwtKeyId: fedcbazyxwvutsrqponmlkjihgfedcba <4>
secrets:
clientSecret: secretsecret <5>
privateKey: -----BEGIN RSA PRIVATE KEY-----\nprivatekeyhere\n-----END RSA PRIVATE KEY----- <6>
privateKey: | <6>
-----BEGIN RSA PRIVATE KEY-----
MIIE...
KAgD...
... multiple lines of key data ...
-----END RSA PRIVATE KEY-----
--
<1> Specifies whether the connector uses basic or OAuth authentication.
<2> The user identifier.
<3> The client identifier assigned to the OAuth application.
<4> The key ID assigned to the JWT verifier map of your OAuth application.
<5> The client secret assigned to the OAuth application.
<6> The RSA private key. If it has a password, you must also specify
<6> The RSA private key in multiline format. If it has a password, you must also specify
`privateKeyPassword`.


Expand Down
9 changes: 5 additions & 4 deletions docs/settings/alert-action-settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,9 @@ xpack.actions.customHostSettings:
certificateAuthoritiesFiles: [ 'one.crt' ]
certificateAuthoritiesData: |
-----BEGIN CERTIFICATE-----
... multiple lines of certificate data here ...
MIIDTD...
CwUAMD...
... multiple lines of certificate data ...
-----END CERTIFICATE-----
smtp:
requireTLS: true
Expand Down Expand Up @@ -125,9 +127,8 @@ A file name or list of file names of PEM-encoded certificate files to use
to validate the server.

`xpack.actions.customHostSettings[n].ssl.certificateAuthoritiesData` {ess-icon}::
The contents of a PEM-encoded certificate file, or multiple files appended
into a single string. This configuration can be used for environments where
the files cannot be made available.
The contents of one or more PEM-encoded certificate files in multiline format.
This configuration can be used for environments where the files cannot be made available.

[[action-config-email-domain-allowlist]] `xpack.actions.email.domain_allowlist` {ess-icon}::
A list of allowed email domains which can be used with the email connector. When this setting is not used, all email domains are allowed. When this setting is used, if any email is attempted to be sent that (a) includes an addressee with an email domain that is not in the allowlist, or (b) includes a from address domain that is not in the allowlist, it will fail with a message indicating the email is not allowed.
Expand Down

0 comments on commit 385281b

Please sign in to comment.