From 087d1a3be8e267ee89f8462a1bdee2023cd37fb0 Mon Sep 17 00:00:00 2001 From: mposolda Date: Wed, 12 Apr 2023 12:42:02 +0200 Subject: [PATCH] Remove unused and outdated page for user federation mapper closes #19128 --- .../topics/user-federation-mapper.adoc | 15 --------------- 1 file changed, 15 deletions(-) delete mode 100644 docs/documentation/server_development/topics/user-federation-mapper.adoc diff --git a/docs/documentation/server_development/topics/user-federation-mapper.adoc b/docs/documentation/server_development/topics/user-federation-mapper.adoc deleted file mode 100644 index f2198a9b040..00000000000 --- a/docs/documentation/server_development/topics/user-federation-mapper.adoc +++ /dev/null @@ -1,15 +0,0 @@ -[[_user_federation_mapper]] -== User federation mapper SPI - -=== LDAP mapper - -For the more advanced use cases, you have the possibility to create your own implementation of LDAP mapper or just subclass from some already existing mapper -implementation. You will need to implement `UserFederationMapperFactory` interface. - -In most cases, instead of creating `UserFederationMapperFactory` from scratch, you can create subclasses of `AbstractLDAPFederationMapperFactory`, which itself -implements `UserFederationMapperFactory`. - -Then you need to create mapper implementation, which will be subclass of `AbstractLDAPFederationMapper` (this mapper implementation will be returned by -`YourAbstractLDAPFederationMapperFactorySubclass.createMapper` method). - -For details on how to package and deploy a custom provider refer to the <> chapter.