OpenSearch/all-signatures.txt

@defaultMessage Convert to URI
java.net.URL#getPath()
java.net.URL#getFile()
[cleanup] - added forbidden apis mvn plugin - fixed the use of the found forbidden APIs - changed `FiredAlert.State` values to lower case (for consistency sake) Original commit: elastic/x-pack-elasticsearch@9b3f8383d97c072893884704d5b2b8091941c5a9 2015-02-17 10:31:18 -05:00			`@defaultMessage Convert to URI`
			`java.net.URL#getPath()`
Better handling of sensitive data in registered watches and watcher settings A watch may contain sensitive data that typically you don't want to expose in plain text. Exposing means: - storing it as plain text in the `.watches` and `.watch_history` indices - storing it in memory in plain text (can be access via mem dump) - returning it to the user via API in plain text Examples of such sensitive data: - The `password` for the email service (can be configured on the watch itself) - The `password` for http input when using basic auth - The `passowrd` for webhook action when using basic auth A new `SecretService` (you heard it right... secret service) was added to handel the secrets across the board. When a watch is first added to watcher, this service converts all the sensitive data to secrets. From that moment on, all sensitive data associated with the watch (whether in stored in the index or in memory) is hidden behind the secret. This service is also used to "reveal" the original sensitive data on-demand when needed (for example, when the email is sent, it is sent with the original text). There are two implementations for the `SecretService`. The default one is "plain text" where the created secrets don't really hide anything. The second implementation is based on Shield. If Shield is installed and enabled, the `ShieldSecretService` is used which uses shield's crypto service to potentially encrypt the sensitive data (only potentially because Shield's system key must be defined for encryption to take effect, without the system key, the crypto service will not encrypt and instead return the sensitive data in plain text) Note, even when Shield is installed, the encryption of sensitive data will only be applied if the `watcher.shield.encrypt_sensitive_data` setting is set to `true`. By default it is set to `false`. The `get watch` and `execute watch` APIs were updated to filter out sensitive data (using special "hide secrets" parameter). When shield is integrated, we use shield's settings filter to filter out sensitive settings from the REST nodes info API (when shield is not installed or enabled, we don't do this filtering). For this change several other refactoring needed to take place - The http auth codebase was refactored to be more modular. Just like with other modular constructs in watcher, we separated `HttpAuth` from `ApplicableHttpAuth` where the former is the configuration construct and tha latter is the applicable ("executable") construct. - Changed `WatchStore#put` to accept a watch (instead of the watch source). That's more natural way of looking at a store. Also, a `Watch` can now create and return itself as `ByteReference`. In addition, we now don't directly store the watch source as it was sent by the user, instead, we first parse it to a watch (important step to both validate the source and convert all sensitive data to secrets) and then serialize the watch back to `ByteReference`. This way we're sure that only the secrets are stored and not the original sensitive data. - All `ToXContent` implementation were updated to properly propagate the `Params` Docs were added to the Shield Integration chapter Original commit: elastic/x-pack-elasticsearch@4490fb0ab8218ed3fe2fdc82396762b90b47a0c7 2015-04-24 05:17:59 -04:00			`java.net.URL#getFile()`