You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/authentication/introducing-metadata-service-authentication.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ To enable Metadata Service Authentication:
53
53
54
54
OR
55
55
56
-
- change the Metadata Service `application.yml` configuration file to set `authentication.enabled` to "true" AND
56
+
- change the Metadata Service `application.yaml` configuration file to set `authentication.enabled` to "true" AND
57
57
- change the Frontend Proxy Service `application.config` configuration file to set `metadataService.auth.enabled` to "true"
58
58
59
59
After setting the configuration flag, simply restart the Metadata Service to start enforcing Authentication.
@@ -116,7 +116,7 @@ These changes represent the first milestone in Metadata Service Authentication.
116
116
117
117
That's perfectly fine, for now. Metadata Service Authentication is disabled by default, only enabled if you provide the
118
118
environment variable `METADATA_SERVICE_AUTH_ENABLED` to the `datahub-gms` container or change the `authentication.enabled` to "true"
119
-
inside your DataHub Metadata Service configuration (`application.yml`).
119
+
inside your DataHub Metadata Service configuration (`application.yaml`).
120
120
121
121
That being said, we will be recommending that you enable Authentication for production use cases, to prevent
122
122
arbitrary actors from ingesting metadata into DataHub.
@@ -141,7 +141,7 @@ the root "datahub" user account.
141
141
142
142
### I want to authenticate requests using a custom Authenticator? How do I do this?
143
143
144
-
You can configure DataHub to add your custom **Authenticator** to the **Authentication Chain** by changing the `application.yml` configuration file for the Metadata Service:
144
+
You can configure DataHub to add your custom **Authenticator** to the **Authentication Chain** by changing the `application.yaml` configuration file for the Metadata Service:
Copy file name to clipboardexpand all lines: docs/how/updating-datahub.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -328,7 +328,7 @@ Helm with `--atomic`: In general, it is recommended to not use the `--atomic` se
328
328
329
329
-#6243 apache-ranger authorizer is no longer the core part of DataHub GMS, and it is shifted as plugin. Please refer updated documentation [Configuring Authorization with Apache Ranger](./configuring-authorization-with-apache-ranger.md#configuring-your-datahub-deployment) for configuring `apache-ranger-plugin` in DataHub GMS.
330
330
-#6243 apache-ranger authorizer as plugin is not supported in DataHub Kubernetes deployment.
331
-
-#6243 Authentication and Authorization plugins configuration are removed from [application.yml](../../metadata-service/configuration/src/main/resources/application.yml). Refer documentation [Migration Of Plugins From application.yml](../plugins.md#migration-of-plugins-from-applicationyml) for migrating any existing custom plugins.
331
+
-#6243 Authentication and Authorization plugins configuration are removed from [application.yaml](../../metadata-service/configuration/src/main/resources/application.yaml). Refer documentation [Migration Of Plugins From application.yaml](../plugins.md#migration-of-plugins-from-applicationyml) for migrating any existing custom plugins.
332
332
-`datahub check graph-consistency` command has been removed. It was a beta API that we had considered but decided there are better solutions for this. So removing this.
333
333
-`graphql_url` option of `powerbi-report-server` source deprecated as the options is not used.
334
334
-#6789 BigQuery ingestion: If `enable_legacy_sharded_table_support` is set to False, sharded table names will be suffixed with \_yyyymmdd to make sure they don't clash with non-sharded tables. This means if stateful ingestion is enabled then old sharded tables will be recreated with a new id and attached tags/glossary terms/etc will need to be added again. _This behavior is not enabled by default yet, but will be enabled by default in a future release._
Copy file name to clipboardexpand all lines: docs/plugins.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -252,11 +252,11 @@ All other access are forbidden for the plugin.
252
252
253
253
> Disclaimer: In BETA version your plugin can access any port and can read/write to any location on file system, however you should implement the plugin as per above access permission to keep your plugin compatible with upcoming release of DataHub.
254
254
255
-
## Migration Of Plugins From application.yml
256
-
If you have any custom Authentication or Authorization plugin define in `authorization` or `authentication` section of [application.yml](../metadata-service/configuration/src/main/resources/application.yml) then migrate them as per below steps.
255
+
## Migration Of Plugins From application.yaml
256
+
If you have any custom Authentication or Authorization plugin define in `authorization` or `authentication` section of [application.yaml](../metadata-service/configuration/src/main/resources/application.yaml) then migrate them as per below steps.
257
257
258
258
1. Implement Plugin: For Authentication Plugin follow steps of [Implementing an Authentication Plugin](#implementing-an-authentication-plugin) and for Authorization Plugin follow steps of [Implementing an Authorization Plugin](#implementing-an-authorization-plugin)
259
-
2. Install Plugin: Install the plugins as per steps mentioned in [Plugin Installation](#plugin-installation). Here you need to map the configuration from [application.yml](../metadata-service/configuration/src/main/resources/application.yml) to configuration in `config.yml`. This mapping from `application.yml` to `config.yml` is described below
259
+
2. Install Plugin: Install the plugins as per steps mentioned in [Plugin Installation](#plugin-installation). Here you need to map the configuration from [application.yaml](../metadata-service/configuration/src/main/resources/application.yaml) to configuration in `config.yml`. This mapping from `application.yaml` to `config.yml` is described below
0 commit comments