< prev index next >

src/java.security.jgss/share/classes/org/ietf/jgss/package.html

Print this page 

        
*** 1,10 ****
  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  <html>
  <head>
  <!--
! Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
  DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
  
  This code is free software; you can redistribute it and/or modify it
  under the terms of the GNU General Public License version 2 only, as
  published by the Free Software Foundation.  Oracle designates this
--- 1,10 ----
  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
  <html>
  <head>
  <!--
! Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved.
  DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
  
  This code is free software; you can redistribute it and/or modify it
  under the terms of the GNU General Public License version 2 only, as
  published by the Free Software Foundation.  Oracle designates this

*** 53,66 ****
      peer, authentication is complete. Data protection such as integrity
      and confidentiality can then be obtained from this context.<p>
  
      The GSS-API does not perform any communication with the peer. It merely 
      produces tokens that the application must somehow transport to the
!     other end.<p>
  
  <h3>Credential Acquisition</h3>
! <a name=useSubjectCredsOnly>
      The GSS-API itself does not dictate how an underlying mechanism
      obtains the credentials that are needed for authentication. It is
      assumed that prior to calling the GSS-API, these credentials are
      obtained and stored in a location that the mechanism provider is
      aware of. However, the default model in the Java platform will be
--- 53,66 ----
      peer, authentication is complete. Data protection such as integrity
      and confidentiality can then be obtained from this context.<p>
  
      The GSS-API does not perform any communication with the peer. It merely 
      produces tokens that the application must somehow transport to the
!     other end.
  
  <h3>Credential Acquisition</h3>
! <a name=useSubjectCredsOnly></a>
      The GSS-API itself does not dictate how an underlying mechanism
      obtains the credentials that are needed for authentication. It is
      assumed that prior to calling the GSS-API, these credentials are
      obtained and stored in a location that the mechanism provider is
      aware of. However, the default model in the Java platform will be

*** 95,105 ****
      that are present in the current Subject. However, if this property is
      explicitly set to false by the application, then it indicates that
      the provider is free to use any credentials cache of its choice. Such
      a credential cache might be a disk cache, an in-memory cache, or even
      just the current Subject itself.
- </a>
  
  <h2>Related Documentation</h2>
  <p>
  For an online tutorial on using Java GSS-API, please see
  <a href="../../../../technotes/guides/security/jgss/tutorials/index.html">Introduction to JAAS and Java GSS-API</a>.
--- 95,104 ----



< prev index next >