[xmlsec] Fwd: Use of full DistinguishedName in KeyName
ed.shallow at gmail.com
Wed Oct 19 18:33:23 PDT 2011
OK, here is how it works with mscrypto and xmlsec 1.2.18
<KeyName>CA, GC, PWGSC-TPSGC, "Ed Shallow"</KeyName>
Example 2 with a special character:
<KeyName>CA, GC, PWGSC-TPSGC, "Shallow, Ed"</KeyName>
In other words, do not use the sub-type qualifiers in the DN string i.e. cn=
ou= o= c=
Order is also important.
On Wed, Oct 19, 2011 at 7:38 PM, EdShallow <ed.shallow at gmail.com> wrote:
> 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.
>> On 10/19/11 2:02 PM, EdShallow wrote:
>>> . . . sorry forgot to mention, this behavior is with mscrypto
>>> ---------- 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.
>>> 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?
>>> xmlsec mailing list
>>> xmlsec at aleksey.com
Ed's Contact Information:
Mobile Phone: 613-852-6410
Gmail: ed.shallow at gmail.com
VOIP Address: 107529 at sip.ca1.voip.ms
VOIP DID#: 613-458-5004
Skype ID: edward.shallow
Home Phone: 613-482-2090
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the xmlsec