Re: KITTEN: IETF 75 - 76

Martin Rex <Martin.Rex@sap.com> Wed, 19 August 2009 19:24 UTC

Return-Path: <Martin.Rex@sap.com>
X-Original-To: kitten@core3.amsl.com
Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34BF728C0EC for <kitten@core3.amsl.com>; Wed, 19 Aug 2009 12:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.688
X-Spam-Level:
X-Spam-Status: No, score=-5.688 tagged_above=-999 required=5 tests=[AWL=0.561, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6WJGHM9JwLqg for <kitten@core3.amsl.com>; Wed, 19 Aug 2009 12:24:28 -0700 (PDT)
Received: from smtpde03.sap-ag.de (smtpde03.sap-ag.de [155.56.68.140]) by core3.amsl.com (Postfix) with ESMTP id 58D5F3A6EB8 for <kitten@ietf.org>; Wed, 19 Aug 2009 12:23:55 -0700 (PDT)
Received: from mail.sap.corp by smtpde03.sap-ag.de (26) with ESMTP id n7JJNxJA016742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Aug 2009 21:23:59 +0200 (MEST)
From: Martin Rex <Martin.Rex@sap.com>
Message-Id: <200908191923.n7JJNwWq027044@fs4113.wdf.sap.corp>
Subject: Re: KITTEN: IETF 75 - 76
To: Nicolas.Williams@sun.com
Date: Wed, 19 Aug 2009 21:23:58 +0200
In-Reply-To: <20090819163215.GD1043@Sun.COM> from "Nicolas Williams" at Aug 19, 9 11:32:15 am
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal07
X-SAP: out
Cc: kitten@ietf.org, Shawn.Emery@sun.com
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: martin.rex@sap.com
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2009 19:24:29 -0000

Nicolas Williams wrote:
> 
> > GSS-API is part of the identity selection problem since its the holder  
> > of credentials.
> > 
> > The application/framework will need to drive authentication and select/ 
> > try credentials as it seems approproate and remember what of them was  
> > useful.
> > 
> > This would work today, if it was possible to get initial credentials  
> > and list existing/configured credentials
> 
> Sure.  An iterator following the same design principles as
> gss_display_status() would look like:
> 
> OM_unit32 gss_list_default_cred_names(
> 	OM_uint32 *minor_status,
> 	gss_name_t  *name,
> 	int	    *more
> );

That call looks somewhat restricted to me.

How about something like this:

OM_uint32 gss_list_default_cred_names(
	OM_uint32    * minor_status,
	gss_name_t   * name,
	gss_OID_set  * mech_oids,
	int          * is_default,
	OM_uint32    * cred_context
);

That would also match what you have to feed into an
explicit call to gss_acquire_cred() in order to reliably
get a credentials handle for exactly and each one listed.

-Martin