The new PasswordFetch class offers the ability to retrieve passwords from eDirectory when they are not supplied via the original authentication Method. The workflow diagram shows how PasswordFetch sits in the architecture of the solution:

(Picture TBC)


In this setup example, the following lists the environment configuration:

  • SLES 11 ( –
  • eDirectory 8.8.8 (t=EDIR-TREE)
  • Universal Password Enabled
  • Objects under container: o=DATA
  • Apache running for with SSL enabled
  • Windows Server 2008 R2 ( –
  • Active Directory (dc=ad,dc=domain,dc=com)
  • Domain Controller Server Certificate signed by EDIR-TREE for IDM purposes and AD LDAPS enablement
  • Objects under container: ou=DATA,dc=ad,dc=domain,dc=com
  • Novell Access Manager 3.2.2-77 + IR1-107
  • Administration Console & Identity Provider on SLES 11 x64 ( –
  • Linux Access Gateway ( –
  • The LAG protects the iDP, so the Base URL is
  • Windows 7 x64 SP1
  • Active Directory Member
  • Internet Explorer 9
  • EDIR-TREE Self Signed Certificate Authority imported into Computer Trusted Roots Store
  • * added to IE’s Local Intranet sites

User Stores

Active Directory

Create the User for Kerberos (we will also use this user for AM3 Store Access, so give it sufficient domain access).


The User Login Name must be HTTP/ followed by the Access Manager Base URL domain (i.e. HTTP/


For this next screen, you will need to enable Advanced Features in MMC.


Now we need to export the Kerberos Key Tab file:



Create the test user in ou=IDENTITIES,o=DATA and allow IDM to synchronise the user to Active Directory. This will result in:

  • eDirectory Account: cn=bwalter,ou=IDENTITIES,o=DATA
  • Active Directory Account: cn=Ben Walter,ou=IDENTITIES,ou=DATA,dc=ad,dc=domain,dc=com

IDM will write back the DirXML-ADContext value of cn=Ben Walter,ou=IDENTITIES,ou=DATA,dc=ad,dc=domain,dc=com to the cn=bwalter,ou=IDENTITIES,o=DATA object (we will use this attribute as part of the PasswordFetch class).

Access Manager iDP

First, we create the primary store which will be Active Directory.


Next, we need to create the eDirectory store for the PasswordFetch class to use.


Next, we create the Kerberos Class called “Kerberos”. In the Properties, we add the following values to match with Active Directory:


The bcsLogin.conf looks like: { required

While here, we also create the PasswordFetch Class called “PasswordFetch”. In the Properties, we add the following values:


So, when the Kerberos Token is received by the iDP from the client, it validates with Active Directory (based on userPrincipalName in the token – bwalter@AD.DOMAIN.COM), this returns the DN of the user object (cn=Ben Walter,ou=IDENTITIES,ou=DATA,dc=ad,dc=domain,dc=com). To find the equivalent user in eDirectory, we use this to search for them from the DirXML-ADContext value.

11:20:29 A122EB70 LDAP: ( Search request:
   base: "o=DATA"
   scope:2 dereference:3 sizelimit:0 timelimit:0 attrsonly:0
   filter: "(&(objectClass=Person)(DirXML-ADContext=cn=Ben Walter,ou=IDENTITIES,ou=DATA,dc=ad,dc=domain,dc=com))"
   attribute: "GUID"
   attribute: "fullname"

For each Class, we create a Method:

The Kerberos Method uses the Active Directory Store.


The PasswordFetch Method uses the eDirectory Store.


The options to Overwrite User values means that the LDAP DN will be that of eDirectory, not Active Directory (should it be needed).

Now we create the Contract to be utilised:



Because we told the PasswordFetch Method to overwrite the user values, any policy should use the eDirectory values for LDAP. i.e.:


Internal/External Scenario

Consider the situation where your business has one Access Manager solution for both Internal and External resources. The Internal resources utilise the method described above for single sign on, but what about External Users? They have no Kerberos token to send through!

What we need to do is provide a “fallback” class for External Users so they are prompted to authenticate when no Kerberos Token is received. Kerberos Method Properties Example:


The Catch! The iDP still needs an authentication header passed to the Kerberos Contract, even if its empty, otherwise it errors requiring authentication. To do this, the external clients must be configured like internal clients (i.e. setting Internet Explorer to enable Integrated Login and add the domain to the Intranet Sites, or setting the network.negotiate-auth.delegation-uris and network.negotiate-auth.trusted-uris in Firefox)

More articles on my Website.

2 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 5 (2 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply


  • TellierS says:

    Hi, I have the same setup, but I’m not able to use a policy with a condition check for a container, a group or a role with a validation in eDir to authorize user access.

    • ScorpionSting says:

      To have policies that check eDir values, you *MUST* enable “Overwrite Temporary User” and “Overwrite Real User” in the PFC Method, *AND* disable “Retain Previous Principal” in the PFC Class.

  • cervel0 says:

    Great article. Is it possible to do kerberos constrained delegation with NAM?

  • kkyen says:

    Is this applicable to NAM304? As i don’t see the PasswordFetch class in there… Thx

    • TellierS says:

      A class developped by Bart Andries exist for 3.0.4, I think.

      • ScorpionSting says:

        Bart’s one operates differently to the Novell one and doesn’t contain some of its features such as Principal Replacement.

        You do realise that, if you have any issues with your Access Manager environment, the first thing Novell will ask is what release you’re running? They only offer decent support if you’re running the current release, otherwise they’ll just say “upgrade to current release and see if issue continues”.

  • mus75 says:

    Hi there,
    I’m using NAM to authenticate external users to access to some applications hosted on the cloud (sales force), for the internal users, when they want to access those apps, an additional authentication (besides windows (AD) authentication) is required.
    How can I authorize internal users to access to those applications once they are logged in to the local domain without entering additional login/password using Kerberos (SSO) ?

  • kkyen says:

    What if I’m going to setup the password fetch now and my existing eDirectory is without “Simple Password” or “Universal Password”, can these users be fetch? Thanks.

  • 6525036 says:

    A note on the keytab location
    In this article it is :

    I suppose in later versions of access manager (Iused the appliance), it should be

  • mcurrie says:

    Hi, I have NAM4 setup for the external domain, but the internal AD domain is acme.local, so will it work if the login name is HTTP/ or will I need another NAM instance in the AD domain? The internal name for the server in DNS is vnam40app.acme.local. Thanks.

Apr 11, 2011
10:20 am