shibboleth-dev - Re: authentication strength
Subject: Shibboleth Developers
List archive
- From: "Tom Scavo" <>
- To:
- Cc: "" <>, mace-dir <>
- Subject: Re: authentication strength
- Date: Sat, 25 Mar 2006 17:07:08 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Vwq7aVCD+OXTxC+16U5zg4h6PzwjMQWiFHq9mr1T3j4kgo7AqlaJFNpt/oktvBcBZ49b9zsV3TAfCEdeIzdL32PFrp+U1GxZOcRhsiAV8E/T02+WCOcSbyOzRhnwIvadEOPQLv6MCl5ASZImzAci2yHFdYK0addjOtnZdu/iX5Y=
On 2/16/06, Keith Hazelton
<>
wrote:
>
> ... the name of the attribute is whatever it's
> OID is (all X.500 and LDAP attributes should have OIDs), and the value,
> if it is UTF8, is just the UTF8 string, unaltered. If we create an LDAP
> attribute to carry AuthnLOA, it will have an OID, and a two-part string
> value (syntax TBD) corresponding to the two components, LOA convention
> identifier and LOA value within that convention.
A possible syntax for this new LDAP attribute mirrors that of
'labeledURI', an inetOrgPerson attribute. See the eduPerson spec for
details. Basically, a space is used as a separator since URIs may not
contain spaces.
Tom
- Re: authentication strength, David Chadwick, 03/09/2006
- Re: authentication strength, Tom Scavo, 03/09/2006
- <Possible follow-up(s)>
- Re: authentication strength, Tom Scavo, 03/25/2006
Archive powered by MHonArc 2.6.16.