Issue Details (XML | Word | Printable)

Key: DIRSERVER-768
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Ralf Hauser
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Directory ApacheDS

privide debug output in org.apache.directory.server.core.authn.AuthenticationService.checkAuthenticated()

Created: 25/Oct/06 04:37 AM   Updated: 15/Feb/09 01:36 PM
Return to search
Component/s: None
Affects Version/s: 1.0
Fix Version/s: 1.5.3

Time Tracking:
Not Specified

Environment: all

Resolution Date: 12/May/08 05:28 PM


 Description  « Hide
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

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Ralf Hauser added a comment - 31/Oct/06 08:27 PM
 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]}

Emmanuel Lecharny added a comment - 25/Jan/07 04:01 PM
Sounds a good idea. However, it has been pusched to 1.5 ersion

Alex Karasulu added a comment - 23/Feb/07 08:22 PM
How about a patch attachment Ralf?

Emmanuel Lecharny added a comment - 20/Mar/07 10:14 PM
Not very simple to implement, unless we have some more contextual information. Not vital too. Postponed to 1.5.2

Emmanuel Lecharny added a comment - 01/Apr/08 02:56 PM
Postponed again...

Emmanuel Lecharny added a comment - 12/May/08 05:28 PM
Some log has been added so that the Principal and the Operation are dumped if some unauthenticated user tries to do something not allowed.

The Credentials is never kept in memory for security reasons, so it's always discared and can't be dumped.

Fixed in
http://svn.apache.org/viewvc?rev=655571&view=rev
http://svn.apache.org/viewvc?rev=655572&view=rev

Emmanuel Lecharny added a comment - 15/Feb/09 01:36 PM
closed