directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralf Hauser (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-768) privide debug output in org.apache.directory.server.core.authn.AuthenticationService.checkAuthenticated()
Date Tue, 31 Oct 2006 20:28:17 GMT
    [ http://issues.apache.org/jira/browse/DIRSERVER-768?page=comments#action_12446047 ] 
            
Ralf Hauser commented on DIRSERVER-768:
---------------------------------------

 java.lang.IllegalStateException: Attempted operation by unauthenticated caller.
	at org.apache.directory.server.core.authn.AuthenticationService.checkAuthenticated(AuthenticationService.java:434)
	at org.apache.directory.server.core.authn.AuthenticationService.hasEntry(AuthenticationService.java:257)
	at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.hasEntry(InterceptorChain.java:1326)
	... 30 more

is what I am getting.

- what "operation" did it attempt to undertake?
- which caller? It appears that it is ServerLdapContext
- in ctx.env, there is a principal but apparently no Context.SECURITY_CREDENTIALS ("java.naming.security.credentials"),
but this also should not cause the execption
{java.naming.factory.initial=org.apache.directory.server.jndi.ServerContextFactory, java.naming.provider.url=ou=system,
java.naming.security.principal=uid=admin,ou=system, java.naming.security.authentication=simple,
org.apache.directory.server.core.configuration.Configuration=org.apache.directory.server.configuration.MutableServerStartupConfiguration@883644,
java.naming.ldap.attributes.binary=[bytecode, 1.2.6.1.4.1.18060.1.1.1.3.22, userpassword,
1.3.6.1.4.1.42.2.27.4.1.8, usersmimecertificate, deltarevocationlist, personalsignature, krb5key,
2.5.4.40, 1.3.6.1.4.1.3401.8.2.3, 0.9.2342.19200300.100.1.7, pgprecondata, 2.5.4.35, photo,
crosscertificatepair, 1.3.6.1.4.1.3401.8.2.6, supportedalgorithms, pgpdata, 0.9.2342.19200300.100.1.55,
2.5.4.38, userpkcs12, 0.9.2342.19200300.100.1.60, javaserializeddata, 1.3.6.1.4.1.5322.10.1.10,
2.5.4.37, 2.16.840.1.113730.3.1.40, cacertificate, authorityrevocationlist, certificaterevocationlist,
audio, jpegphoto, 2.5.4.52, 2.5.4.36, 2.16.840.1.113730.3.1.216, 2.5.4.53, 2.5.4.39, usercertificate,
0.9.2342.19200300.100.1.53]}


> privide debug output in org.apache.directory.server.core.authn.AuthenticationService.checkAuthenticated()
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-768
>                 URL: http://issues.apache.org/jira/browse/DIRSERVER-768
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: all
>            Reporter: Ralf Hauser
>
> it would be very useful to know whether 
> - a principal was found at all
> - if so, which one and
> - whether it contained SECURITY_CREDENTIALS
> This debug output furthermore could provide some more hint (url to a man page/readme)
where to find more about the error codes such as 
> - "Loop detected (54)" 
> - or 
>    ldap_bind: Internal (implementation specific) error (80)
>         additional info: Bind failed: Unexpected exception.
> see also DIRSERVER-763

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message