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" <[email protected]> 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" <[email protected] <mailto:[email protected]>> >> Date: Oct 19, 2011 3:55 PM >> Subject: Use of full DistinguishedName in KeyName >> To: "[email protected] <mailto:[email protected]>" <[email protected] >> <mailto:[email protected]>> >> >> 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 >> [email protected] >> http://www.aleksey.com/**mailman/listinfo/xmlsec<http://www.aleksey.com/mailman/listinfo/xmlsec> >> >
_______________________________________________ xmlsec mailing list [email protected] http://www.aleksey.com/mailman/listinfo/xmlsec
