The following table lists the known issues in Security.
Table 25 Known Issues in Security
Problem ID |
Description |
---|---|
4671445 |
Sun Java System Web Server cannot connect to an LDAP server over SSL if LDAP client authentication is required. If Sun Java System Web Server contacts an LDAP server that requires client authentication (in this case, the web server is the client), the web server’s certificate cannot be sent and access will fail. |
4863599 |
Cannot use the same group name under different organizational units. If the same group name is used and you try to restrict access with the group name, Sun Java System Web Server returns an error when clients try to access the site. Workaround: Use a different group name for each organizational unit. |
4963468 |
In some circumstances, the “list” right has no effect on directory listing. According to Chapter 9, Controlling Access to Your Server, in Sun Java System Web Server 6.1 SP11 Administrator’s Guide, the “list” right is required to obtain directory listings from directories that do not contain an index file. However, in certain circumstances you can obtain a directory listing even if the applicable ACLs deny the list right. If you need to restrict directory indexing, disable indexing, as discussed in Chapter 16, Content Management, in Sun Java System Web Server 6.1 SP11 Administrator’s Guide, instead of or in addition to denying the list right. |
6310956 6298215 |
When LDAP drops the connection because of inactivity, for example, timeout set on the LDAP, web server is unable to re-initialize the connection to LDAP. This problem only occurs when web server is installed as part of the JES3/JES4 install. The problem does not exist in stand-alone (file-based) installation. Workaround:
|