Configuring Writable LDAP in IBM Developer Portal
Key Points
- Verify that the developer portal’s user registry is delegated to the UM catalog before beginning LDAP configuration.
- Install and enable the three required modules—LDAP authentication, LDAP servers, and LDAP user—to support LDAP integration.
- In the LDAP server configuration, set a unique machine name, enable “Use OpenLDAP,” specify the server’s IP/domain and port (389), enable service‑account bind, and provide the bind DN and password.
- Define the LDAP‑to‑Drupal user relationship (e.g., OU=people, domain name, name and email attributes, and user DN expression) and test the connection to confirm successful binding.
- Configure People → LDAP settings to select the new LDAP server, enable user creation/synchronization options, handle account conflicts, and apply the default mappings (referencing the Knowledge Center), then save the configuration.
Full Transcript
# Configuring Writable LDAP in IBM Developer Portal **Source:** [https://www.youtube.com/watch?v=dETTvSdODjc](https://www.youtube.com/watch?v=dETTvSdODjc) **Duration:** 00:10:58 ## Summary - Verify that the developer portal’s user registry is delegated to the UM catalog before beginning LDAP configuration. - Install and enable the three required modules—LDAP authentication, LDAP servers, and LDAP user—to support LDAP integration. - In the LDAP server configuration, set a unique machine name, enable “Use OpenLDAP,” specify the server’s IP/domain and port (389), enable service‑account bind, and provide the bind DN and password. - Define the LDAP‑to‑Drupal user relationship (e.g., OU=people, domain name, name and email attributes, and user DN expression) and test the connection to confirm successful binding. - Configure People → LDAP settings to select the new LDAP server, enable user creation/synchronization options, handle account conflicts, and apply the default mappings (referencing the Knowledge Center), then save the configuration. ## Sections - [00:00:00](https://www.youtube.com/watch?v=dETTvSdODjc&t=0s) **Configuring Writable LDAP in IBM Portal** - A step‑by‑step walkthrough showing how to set up a writable LDAP server in the IBM Developer Portal, covering registry selection, required module activation, connection and bind configuration, and testing the server. ## Full Transcript
in this demonstration I'm going to show
you how to configure a writable ldap
server in the IBM developer portal so
the first step here is to ensure that
your um catalog for which you've got
your developer portal for has the portal
delegated user registry configured as um
the user
registry the next step is to configure
the modules that you need so to module
and the modules you need are ldap
authentication ldap
servers and ldap
user and
save the next step is to
configure configuration
ation
people elap
configuration
servers and here I need to add an ldap
server
configuration the first section I need
to do is the connection settings
tab so choose a unique machine
name
I want this
enabled and I want to use open
elap alongside the ldap server that I'm
going to
use and this is the IP or domain name of
my ldap server and I know that I have
created my ldap server using uh port
389 so that section is completed I now
need to fill F in my binding method and
for this I need to ensure that I've got
service account bind
enabled and now I need to configure DN
for non anonymous search and in this
case it
is as
so and then just Supply the password for
my
server the next section is the L app us
to Drupal user
relationship in this
case it is OU equals
people and my specific domain name or
name
attribute email
attribute and the expression for user
DN all finished
I'm now going to
add so I now have uh L app server
configured and
added before I go any further I am now
going to test my
server from the test page we don't
really need to put any of these um
values in here just click the test
button here
here and we can see that it uh using the
settings I given it it's binding uh
successfully um and so it's now worth
going on to test um test and configure
the rest of the the ldap
setup so configuration people ldap and
now I want to go to three
user in the basic provisioning I need to
choose my L app server which is the one
that I configured previously and I need
that
one and to check that these two options
have been enabled create or sync to
Drupal user on success or authentication
with Lup credentials and create or sync
to Drupal user anytime a Drupal user
account is created or
updated also checking that this has been
enabled so if there's a user account
conflict associate Drupal account with
the El app entry also by default the the
correct option here has been selected
account creation settings at admin
config people account settings do not
affect elap Associated Drupal
accounts and furthermore down
here is to perform no action but email
list of orphaned
accounts and that is selected too so the
defaults um for the last few options are
correct now we need to um do some of the
mappings um this is quite a lengthy
process um I'd advise um referring to
Knowledge Center for the exact
mappings the first thing I am going to
do though is just
save and by saving that some of my
mappings are automatically configured so
um just to
recap do the um the the original
settings here by selecting your server
ensuring that the right options have
been chosen and then save and so some of
the mappings are already created for you
in this case I just have to configure
another uh two
settings given a
name and select that to first name
and that's SN to last
name and save
those I now have the provision from ldap
to Drupal mappings
completed and now need to fill
in the basic provisioning to Lup
settings
and save
again again ensure that the L app server
is
selected and I need to select the create
all sync to elap entry options here for
my entry provisioning
events and now I have a large table uh
to configure
here
so um I'm just going to pause for a
moment and I'll get my eight mappings
created I have my first four mappings
created here and I've need to uh map
another four
so
save back down again and it's now after
I've done that save has now created
another four entries for me to fill
in in fact I realized got just one more
to do so another
save and then I'll just scroll down
finish
up and the last one is password user
only in fact I think I've just done the
wrong one
there and just modify that
um so that's all my settings um mappings
done and now we've got one last thing to
do which is go to the authentication
Tab and in the allab
authentications I'm only going to allow
ldap
authentication um so previously I've
allowed a mix mode a dupal
authentication with whatever provider um
but I'm only allowing uh ldap
authentication now except for user one
which is the user I currently am which
is
admin and I'm going to also select my
Lup
server and down here
save so all ready to try with my our
first
user so now I'm logged out and I want to
log in as a uh new new
user create an account and my username
is going to be
Andre and I am going to be
Andre
example.com
password and finish off with my
capture
create new
account I am now logged in um as Andre
and my organization is called Andre
example now I'm just going to hop over
to my L app
server and you can see I already have
two users here called Bob and Mary uh
prior users and if I just refresh I
should now see yes I can now see my new
user
Andre and the values I was
given previously
are
added so if I log out
Andre and log
in and uh this is a previous US user
that is on This ldap
Server so there you have
it writable ldap is now possible uh in
the developer portal by use of using the
portal delegated user
registry and by enabling the correct
modules and configuration in the
portal