- java.lang.Object
-
- org.ietf.jgss.ChannelBinding
-
public class ChannelBinding extends Object
This class encapsulates the concept of caller-provided channel binding information. Channel bindings are used to strengthen the quality with which peer entity authentication is provided during context establishment. They enable the GSS-API callers to bind the establishment of the security context to relevant characteristics like addresses or to application specific data.The caller initiating the security context must determine the appropriate channel binding values to set in the GSSContext object. The acceptor must provide an identical binding in order to validate that received tokens possess correct channel-related characteristics.
Use of channel bindings is optional in GSS-API. ChannelBinding can be set for the
GSSContext
using thesetChannelBinding
method before the first call toinitSecContext
oracceptSecContext
has been performed. Unless thesetChannelBinding
method has been used to set the ChannelBinding for a GSSContext object,null
ChannelBinding will be assumed.Conceptually, the GSS-API concatenates the initiator and acceptor address information, and the application supplied byte array to form an octet string. The mechanism calculates a MIC over this octet string and binds the MIC to the context establishment token emitted by
initSecContext
method of theGSSContext
interface. The same bindings are set by the context acceptor for itsGSSContext
object and during processing of theacceptSecContext
method a MIC is calculated in the same way. The calculated MIC is compared with that found in the token, and if the MICs differ, accept will throw aGSSException
with the major code set toBAD_BINDINGS
, and the context will not be established. Some mechanisms may include the actual channel binding data in the token (rather than just a MIC); applications should therefore not use confidential data as channel-binding components.Individual mechanisms may impose additional constraints on addresses that may appear in channel bindings. For example, a mechanism may verify that the initiator address field of the channel binding contains the correct network address of the host system. Portable applications should therefore ensure that they either provide correct information for the address fields, or omit setting of the addressing information.
- Since:
- 1.4
-
-
Constructor Summary
Constructors Constructor and Description ChannelBinding(byte[] appData)
Creates a ChannelBinding object without any addressing information.ChannelBinding(InetAddress initAddr, InetAddress acceptAddr, byte[] appData)
Create a ChannelBinding object with user supplied address information and data.
-
Method Summary
Methods Modifier and Type Method and Description boolean
equals(Object obj)
Compares two instances of ChannelBinding.InetAddress
getAcceptorAddress()
Get the acceptor's address for this channel binding.byte[]
getApplicationData()
Get the application specified data for this channel binding.InetAddress
getInitiatorAddress()
Get the initiator's address for this channel binding.int
hashCode()
Returns a hashcode value for this ChannelBinding object.
-
-
-
Constructor Detail
-
ChannelBinding
public ChannelBinding(InetAddress initAddr, InetAddress acceptAddr, byte[] appData)
Create a ChannelBinding object with user supplied address information and data.null
values can be used for any fields which the application does not want to specify.- Parameters:
initAddr
- the address of the context initiator.null
value can be supplied to indicate that the application does not want to set this value.acceptAddr
- the address of the context acceptor.null
value can be supplied to indicate that the application does not want to set this value.appData
- application supplied data to be used as part of the channel bindings.null
value can be supplied to indicate that the application does not want to set this value.
-
ChannelBinding
public ChannelBinding(byte[] appData)
Creates a ChannelBinding object without any addressing information.- Parameters:
appData
- application supplied data to be used as part of the channel bindings.
-
-
Method Detail
-
getInitiatorAddress
public InetAddress getInitiatorAddress()
Get the initiator's address for this channel binding.- Returns:
- the initiator's address.
null
is returned if the address has not been set.
-
getAcceptorAddress
public InetAddress getAcceptorAddress()
Get the acceptor's address for this channel binding.- Returns:
- the acceptor's address. null is returned if the address has not been set.
-
getApplicationData
public byte[] getApplicationData()
Get the application specified data for this channel binding.- Returns:
- the application data being used as part of the
ChannelBinding.
null
is returned if no application data has been specified for the channel binding.
-
equals
public boolean equals(Object obj)
Compares two instances of ChannelBinding.- Overrides:
equals
in classObject
- Parameters:
obj
- another ChannelBinding to compare this one with- Returns:
- true if the two ChannelBinding's contain the same values for the initiator and acceptor addresses and the application data.
- See Also:
Object.hashCode()
,HashMap
-
hashCode
public int hashCode()
Returns a hashcode value for this ChannelBinding object.- Overrides:
hashCode
in classObject
- Returns:
- a hashCode value
- See Also:
Object.equals(java.lang.Object)
,System.identityHashCode(java.lang.Object)
-
-
Document created the 11/06/2005, last modified the 04/03/2020
Source of the printed document:https://www.gaudry.be/en/java-api-rf-org/ietf/jgss/ChannelBinding.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.