IY69937: DOC - IPLANET DIRECTORY ENTRY FOR SECAUTHORITY=DEFAULT WAS NOT AUTOMATICALLY CREATED, PDCONFIG FOR POLICY SERVER FAILED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • PMR: 74221,L6Q,000
    
    Problem Description:
    
    TAM v510 with LA-0012 installed  PDcofig for policy server fails
    with
    msg - error code 0X20 was received from LDAP.  We are using
    iplanet
    version 5.2 for LDAP
    
    We then created an ldif file with the information to add the
    "secAuthority=Default" dn to the LDAP. After which time the
    pdconfig
    was able to complete sucessfully.
    
    I could not find any documentation any where that we need to
    "pre-load" the "secAuthority=Default" record into the LDAP
    before
    begining the pdconfig.
    
    Workaround:
    
    
    1) create a LDIF file (secAuth.ldif)  that contains:
    
    dn: secAuthority=Default
    objectclass: secAuthorityInfo
    objectclass: eApplicationSystem
    objectclass: eSystem
    objectclass: cimLogicalElement
    objectclass: cimManagedSystemElement
    objectclass: cimManagedElement
    objectclass: top
    secAuthority: Default
    version: 3.0
    
    2) run a ldapmodify -a -c -D cn=root -w <secretpassword>  -f
    secAuth.ldif
    

Local fix

  • manually create ldap entry
    

Problem summary

  • see main problem description
    

Problem conclusion

  • In our TAM 5.1 Base Installation Guide page
    86 under section "Setting up Sun One Directory Server", the dire
    ctions for creating suffix "secAuthority=Default" using Sun One
    Console (i.e. GUI) are described.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY69937

  • Reported component name

    ACCESS MGR E-BU

  • Reported component ID

    5724C0800

  • Reported release

    510

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-04-05

  • Closed date

    2005-04-17

  • Last modified date

    2005-04-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Security Access Manager for Web

Software version:

510

Reference #:

IY69937

Modified date:

2005-04-17

Translate my page

Machine Translation

Content navigation