[
https://issues.apache.org/jira/browse/RIVER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon IJskes updated RIVER-15:
------------------------------
Assignee: (was: Mark Brouwer)
> Provide context information for logging in
> com.sun.jini.discovery.internal.X500Provider
> ---------------------------------------------------------------------------------------
>
> Key: RIVER-15
> URL: https://issues.apache.org/jira/browse/RIVER-15
> Project: River
> Issue Type: Improvement
> Components: com_sun_jini_discovery
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Priority: Minor
>
> The detailed logging for discovery is hard to read/unscramble to to a lack of
> context information at some points, see the example below:
> {noformat:nopanel}
> 24-Mar-2007 19:29:47 com.sun.jini.discovery.internal.X500Provider
> getPrivateCredentials (oid=1.3.6.1.4.12543.2.0, instance=master)
> FINEST: obtained private credentials []
> 24-Mar-2007 19:29:47 com.sun.jini.discovery.internal.X500Provider
> getPrivateCredentials (oid=1.3.6.1.4.12543.2.0, instance=master)
> FINEST: obtained private credentials
> [javax.security.auth.x500.X500PrivateCredential@1bbea67,
> javax.security.auth.x500.X500PrivateCredential@1a2cc7]
> {noformat}
> It took me stepping through a debugger to finally understand that the first
> {{getPrivateCredentials}} was for the RSA key algorithm and the second for
> the DSA key algorithm, so in this case the
> {{X500Provider.getPrivateCredentials}} method should have added the algoritm
> in the logging.
> Also {{X500PrivateCredential}} has no proper string representation, so
> logging those is not very helpful. To me it seems that for logging purposes
> it is better to display the X.500 principal associated with the X.509
> certificate from the private credentials.
--
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
