This area isn't well served - for future posters, he is not trying to
authenticate against LDAP, nor against AD. He wants users to be
identified by their own organization and identity information passed
back to his site from the partners AD.
The thing with SAML is that there are lots of different Profiles and
Transports that describe precisely how to communicate with an Identity
Provider. The plus side for you is that you are implementing a Service
Provider (SP) and not as an Identity Provider (IdP) - ie you have a
site that people log in to, not a site that stores and provides
identity information.
You will need to determine what interop support ADFS has for SAML 2.0,
what Profiles and Transports it expects to use.
I don't know much about the libraries you mentioned. We used py-lasso,
which is a library for producing, interpreting, signing/validating and
encrypting/decrypting SAML messages. The documentation was ..... less
than good. In the most part we relied on reading the C sources to
lasso and the SWIG bindings to determine what functions to call and
when.
Plus, we were not doing interop, we were writing our own IdP that
talked to our own SPs, so we had complete blanket choice over what
Profiles to use.
I do not think you can achieve this by simply "Install this package,
add this setting". Happy to be told otherwise!
Cheers
Tom