From 4b87f23d20f3d630cb5f4a6478fec90ef9ddc6b2 Mon Sep 17 00:00:00 2001 From: David Weber Date: Thu, 30 May 2024 21:04:16 +0200 Subject: [PATCH] docs: ldap module correct usage of legacy provider Signed-off-by: David Weber --- docs/integrations/ldap/org--old.md | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-) diff --git a/docs/integrations/ldap/org--old.md b/docs/integrations/ldap/org--old.md index 13fbcb9408..63f052371f 100644 --- a/docs/integrations/ldap/org--old.md +++ b/docs/integrations/ldap/org--old.md @@ -52,7 +52,7 @@ export default async function createPlugin( // The target parameter below needs to match the ldap.providers.target // value specified in your app-config. builder.addEntityProvider( - LdapOrgEntityProvider.fromConfig(env.config, { + LdapOrgEntityProvider.fromLegacyConfig(env.config, { id: 'our-ldap-master', target: 'ldaps://ds.example.net', logger: env.logger, @@ -343,12 +343,15 @@ the group transformer. 2. Configure the provider with the transformer: ```ts - const ldapEntityProvider = LdapOrgEntityProvider.fromConfig(env.config, { - id: 'our-ldap-master', - target: 'ldaps://ds.example.net', - logger: env.logger, - groupTransformer: myGroupTransformer, - }); + const ldapEntityProvider = LdapOrgEntityProvider.fromLegacyConfig( + env.config, + { + id: 'our-ldap-master', + target: 'ldaps://ds.example.net', + logger: env.logger, + groupTransformer: myGroupTransformer, + }, + ); ``` ## Using a Processor instead of a Provider @@ -368,7 +371,7 @@ register it in the catalog plugin: ```typescript title="packages/backend/src/plugins/catalog.ts" builder.addProcessor( - LdapOrgReaderProcessor.fromConfig(env.config, { + LdapOrgReaderProcessor.fromLegacyConfig(env.config, { logger: env.logger, }), );