[xmlsec] Fwd: Use of full DistinguishedName in KeyName
EdShallow
ed.shallow at gmail.com
Wed Oct 19 16:38:21 PDT 2011
OK. Give me a day or so and I will check the source to see if anything has
changed in the CAPI calls.
On Oct 19, 2011 7:29 PM, "Aleksey Sanin" <aleksey at aleksey.com> wrote:
> Not that I am aware of.
>
> Aleksey
>
> On 10/19/11 2:02 PM, EdShallow wrote:
>
>> . . . sorry forgot to mention, this behavior is with mscrypto
>> Ed
>>
>> ---------- Forwarded message ----------
>> From: "EdShallow" <ed.shallow at gmail.com <mailto:ed.shallow at gmail.com>>
>> Date: Oct 19, 2011 3:55 PM
>> Subject: Use of full DistinguishedName in KeyName
>> To: "xmlsec at aleksey.com <mailto:xmlsec at aleksey.com>" <xmlsec at aleksey.com
>> <mailto:xmlsec at aleksey.com>>
>>
>> Hi Aleksey,
>>
>> Use of full DN in KeyName template element used to work in oldwr
>> versions of xmlsec.
>>
>> As of 1.2.18 I can only get CommonName to work.
>>
>> Example:
>> This works
>> <KeyName>Shallow Ed</KeyName>
>>
>> This does not:
>> <KeyName>cn=Shallow Ed,ou=finance,o=acme,c=ca</**KeyName>
>>
>> I receive an "Object or property cannot be found" message.
>>
>> Are there any constraints for naming?
>>
>> Ed
>>
>>
>>
>> ______________________________**_________________
>> xmlsec mailing list
>> xmlsec at aleksey.com
>> http://www.aleksey.com/**mailman/listinfo/xmlsec<http://www.aleksey.com/mailman/listinfo/xmlsec>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.aleksey.com/pipermail/xmlsec/attachments/20111019/421a11ae/attachment.html>
More information about the xmlsec
mailing list