APAR status |
Closed as program error.
| Error description
The problem with using bluepages occurs since the first
attribute in DN is not searchable even it should be always
searchable. What we are proposing to deal with this kind of
directory defects is to search DN after RDN query fails. This
way, I do not break current working functionalities, and make
some improperly structured directory working with some
limitations. Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server security *
* users with LDAP as a user registry when *
* the LDAP schema has an attribute which is *
* not searchable in the DN. *
****************************************************************
* PROBLEM DESCRIPTION: Security can not query relative DN *
* from LDAP with if any attributes of the *
* DN are not searchable. *
****************************************************************
* RECOMMENDATION: Properly configure Ldap to make attributes *
* in DN searchable. *
* This is not a WebSphere defect, and we try *
* give customers with improperly configured *
* ldap some leverages. The support of this *
* kind of ldap is limited, and some *
* functionalities such as SSO with non *
* WebSphere application may loss. The *
* long term solution for this kind of *
* problem is to fix the ldap server to make *
* attributes in DN searchable. *
****************************************************************
If the first attrribute of the DN is not searchable,
WebSphere is unable to query relative DN to perform name
normalization. This may be caused by multiple reasons.
Secureway 3.2.2, 3.1.1 and possibly other versions have a
defect which makes this attribute unsearchable. Some OEM LDAP
servers may also have this defect. Also, configuration
errors can cuase this issue. Some LDAP servers may need
to be configured to make specific attributes searchable.
Some LDAP servers are configured to require a Bind DN before
certain attributes can be searched as well. Problem conclusion
If Relative DN is non-searchable, WebSphere will query DN
itself and use this result. However, if the Relative DN
search fails, and the full DN search is used, SSO may not
function with WebSeal or Domino. If this problem occurs,
the only resolution is to make the Relative DN searchable. Temporary fix
test internally Comments
APAR information | APAR number | PQ67823 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-11-01 | Closed date | 2002-11-01 | Last modified date | 2002-11-01 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
PQ67828
Modules/Macros APAR is sysrouted TO one or more of the following:PQ67828Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED AI | Fixed component ID | 5648C8400 |
Applicable component levels | R350 PSY | UP |
|