|| at Jan 20, 2015 at 9:03 pm
xmlsec is a major, serious, crazy, difficult to implement specification.
At least, the fully conformant spec is. Because along the path to signing
something (or verifying the signature for something), you can "transform"
the XML. Which can involve XPath selection, XSLT transforms, and one of
multiple forms of canonicalization. I did some work related to Apache
Santuario project, and was surprised along the way to discover that to be
fully conformant, you need XPath 1.0, and XSLT 1.0 support. So - not an
easy task to re-implement. And certainly, the Go primitives aren't going to
get you there.
On Friday, January 16, 2015 at 2:58:50 PM UTC-8, andrey mirtchovski wrote:
I have an XML file. It is *possibly* a response in SAML format from an SSO
(single sign-on service).
I haven't seen a package that does that. I'm using cgo and linking
with xmlsec. Another package that I've seen uses the xmlsec1 command
to do that: https://github.com/mattbaird/gosaml
I wish it was something I could implement natively, though:http://www.w3.org/TR/xmldsig-core/
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/d/optout.