You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2007/03/24 20:35:32 UTC
[jira] Commented: (RIVER-15) Provide context information for
logging in com.sun.jini.discovery.internal.X500Provider
[ https://issues.apache.org/jira/browse/RIVER-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483866 ]
Mark Brouwer commented on RIVER-15:
-----------------------------------
Other classes in {{com.sun.jini.discovery.*}} display private credentials that provides no useful information, for those it seems better to display the X.500 principal too.
> 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
> Reporter: Mark Brouwer
> Assigned To: 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.
-
You can reply to this email to add a comment to the issue online.