directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wu, James C." <James.C...@disney.com>
Subject RE: [jira] [Commented] (DIRAPI-127) org.apache.directory.ldap.client.api.SearchCursorImpl should use normal logger (not "CURSOR")
Date Sat, 06 Apr 2013 00:19:40 GMT
Hi,

I am trying to set up ApacheDS as a KDC. After adding hnelson using the following ldif, I
could not get kinit to get the ticket

	 dn: uid=hnelson,ou=users,dc=example,dc=com
	objectclass: top
	objectclass: person
	objectclass: inetOrgPerson
	objectclass: krb5Principal
	objectclass: krb5KDCEntry
	cn: Horatio Nelson
	sn: Nelson
	uid: hnelson
	userpassword: secret
	krb5PrincipalName: hnelson@EXAMPLE.COM


The log output of ApacheDS show the following output:

	[cloud-user@n7-z01-0a2a0c3a ~]$ [17:15:57] ERROR [org.apache.directory.server.KERBEROS_LOG]
- No timestamp found
	[17:15:57] WARN [org.apache.directory.server.kerberos.protocol.KerberosProtocolHandler] -
Additional pre-authentication required (25)
	[17:15:57] WARN [org.apache.directory.server.KERBEROS_LOG] - Additional pre-authentication
required (25)
	[17:16:00] WARN [org.apache.directory.server.kerberos.protocol.KerberosProtocolHandler] -
Integrity check on decrypted field failed (31)
	[17:16:00] WARN [org.apache.directory.server.KERBEROS_LOG] - Integrity check on decrypted
field failed (31)

Could someone give me some hint?

james





-----Original Message-----
From: Hendy Irawan (JIRA) [mailto:jira@apache.org] 
Sent: Friday, April 05, 2013 10:43 AM
To: dev@directory.apache.org
Subject: [jira] [Commented] (DIRAPI-127) org.apache.directory.ldap.client.api.SearchCursorImpl
should use normal logger (not "CURSOR")


    [ https://issues.apache.org/jira/browse/DIRAPI-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623835#comment-13623835
] 

Hendy Irawan commented on DIRAPI-127:
-------------------------------------

Thank you [~elecharny] :)
                
> org.apache.directory.ldap.client.api.SearchCursorImpl should use 
> normal logger (not "CURSOR")
> ----------------------------------------------------------------------
> -----------------------
>
>                 Key: DIRAPI-127
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-127
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M15
>            Reporter: Hendy Irawan
>
> instead of the currently:
>     private static final Logger LOG_CURSOR = LoggerFactory.getLogger( 
> "CURSOR" ); it should use the standard
>     private static final Logger LOG_CURSOR = LoggerFactory.getLogger( 
> SearchCursorImpl.class ); So it can be controlled consistently just like the other loggers
in the application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators For more information
on JIRA, see: http://www.atlassian.com/software/jira
Mime
View raw message