[jboss-jira] [JBoss JIRA] (ELY-374) Ambiguous application of CredentialCallback

[ https://issues.jboss.org/browse/ELY-374?page=com.atlassian.jira.plugin.sy... ] David Lloyd edited comment on ELY-374 at 11/18/15 7:47 PM: ----------------------------------------------------------- I think the main deciding factor on using a peer {{CredentialCallback}} versus a {{VerifyPeerTrustedCallback}} is, if you have a {{NameCallback}} which provides the peer name in advance, then use {{CredentialCallback}} (or {{EvidenceVerifyCallback}}), else {{VerifyPeerTrustedCallback}}. What makes {{NameCallback}} special is that on the client side, it's used to query the local callback handler to get the name to send to the peer, i.e. it's a local name. On the server side, it is used to tell the callback handler what name the client is using, i.e. it's a peer name. There isn't a flag to distinguish the cases. was (Author: dmlloyd): I think the main deciding factor on using a peer {{CredentialCallback}} versus a {{VerifyPeerTrustedCallback}} is, if you have a {{NameCallback}} for the peer, then use {{CredentialCallback}} (or {{EvidenceVerifyCallback}}), else {{VerifyPeerTrustedCallback}}. What makes {{NameCallback}} special is that on the client side, it's used to query the local callback handler to get the name to send to the peer, i.e. it's a local name. On the server side, it is used to tell the callback handler what name the client is using, i.e. it's a peer name. There isn't a flag to distinguish the cases. -- This message was sent by Atlassian JIRA (v6.4.11#64026)