Details
-
Bug
-
Resolution: Fixed
-
Medium
-
3.4
-
System Date Friday, 11 Nov 2005
System Time 10:30:06
Java Version 1.5.0_04
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.5.0_04-b05
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Client VM
User Name Davidd
User Timezone America/Los_Angeles
User Locale English (United States)
System Encoding Cp1252
Operating System Windows 2000 5.0
OS Architecture x86
Application Server Container Apache Tomcat/5.5.9
Database type mssql
Database JNDI address java:comp/env/jdbc/JiraDS
Total Memory 127
Free Memory 99
Used Memory 28
Uptime 1 minute, 16 seconds
Edition Enterprise
Version 3.4
Build Number 106
Method: StandaloneSystem Date Friday, 11 Nov 2005 System Time 10:30:06 Java Version 1.5.0_04 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.5.0_04-b05 Java Runtime Java(TM) 2 Runtime Environment, Standard Edition Java VM Java HotSpot(TM) Client VM User Name Davidd User Timezone America/Los_Angeles User Locale English (United States) System Encoding Cp1252 Operating System Windows 2000 5.0 OS Architecture x86 Application Server Container Apache Tomcat/5.5.9 Database type mssql Database JNDI address java:comp/env/jdbc/JiraDS Total Memory 127 Free Memory 99 Used Memory 28 Uptime 1 minute, 16 seconds Edition Enterprise Version 3.4 Build Number 106 Method: Standalone
-
3.04
-
Description
LDAP authentication fails using the 'osuser-1.0-dev-patched-log4j-1.4jdk-21Oct05.jar' provided with JIRA 3.4 with the error 'Error initializing SSL/TLS'
Replacing this file with 'osuser-1.0-dev-25May05-log4j-1.4jdk.jar' from JIRA 3.3.3 fixes the problem.
The strange thing is using the 'Configure LDAP authentication' screen works fine. When the output is copied to osuser.xml, however, logging in doesn't work with the same user and password as in the test.
Attachments
Issue Links
- is caused by
-
-
- Closed
-
