PM52362: ADD A CUSTOM PROPERTY TO SUPPORT PRINCIPALNAME FOR LDAP AUTHENTICATION

Fixes are available

APAR status

Closed as program error.

Error description

VMM only uses user's Distinguish Name to bind with LDAP

Local fix

```
NA
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: Virtual Member Manager (VMM) only uses  *
*                      user's Distinguish Name to bind with    *
*                      LDAP                                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In order to communicate with LDAP, Virtual Member Manager (VMM)
must bind itself with LDAP using a user name and password. VMM
limited customers to use Distinguish Name (DN)of the user as
user name in order to bind with the LDAP. If you wanted to use
any other property like uid or samAccountName to bind with
LDAP, then an Authentication exception was thrown.

Problem conclusion

To fix this, you need to set a new custom property
"useInputPrincipalNameForLogin" with value "true". This will
allow you to bind with LDAP using the principal name of the
user (which in turn could be set to any LDAP attribute). In
order to set this property, use the following command:

$AdminTask setIdMgrCustomProperty { -id <LDAP_repos_ID> -name
useInputPrincipalNameForLogin -value true}

Here "LDAP_repos_ID" is the repository id of the LDAP
configured in VMM. Also save the configuration after executing
the above command using:

$AdminConfig save

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.43, 7.0.0.23, 8.0.0.3.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM52362
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-16
Closed date
2011-12-27
Last modified date
2011-12-27

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

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM52362: ADD A CUSTOM PROPERTY TO SUPPORT PRINCIPALNAME FOR LDAP AUTHENTICATION

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

R800 PSY

Document Information

Share your feedback

Need support?