XML Parse error in EntityDescriptor - ADFS metadata file

[socdream]

I'm getting an error while trying to add an identity provider based on an ADFS metadata file, the error is:

{"The specified type was not recognized: name='ApplicationServiceType',
namespace='http://docs.oasis-open.org/wsfed/federation/200706',
at ."}

It comes from the Deserialize method in the Serialization class

[svrooij]

@socdream why would you use this library to try to login with ADFS. This library is for Identity Providers that use SAML2. For ADFS you should check out this package.

[eByte23]

@svrooij why would you not try and use this library, SAML is a universal spec, you can use ADFS as a SAML IDPthis allows you to use and SP app that allows SAML otherwise people would have to implement different types of auth for many IDP types.

I also encountered this issue and I will need to fix it for my implementation.

[zarusz]

@socdream and @eByte23 did you integrate successfully with ADFS and this library (over SAML2.0 protocol)?

What I can tell the library worked well with PingFederate as identity provider, now wondering about ADFS.
My use case requires to use SAML2 protocol and ADFS is one of the target IdP.

[eByte23]

Hi, Yes i successfully did this in my fork, there were changes that needed to be made to serialize tge metadata correctly.  Its quite simple to setup just create an endpoint that serves the metadata. The consume adfs metadata and i use a persistent nameid transform in adfs to map the username through to nameid format with persistent. If you need any further details let me know Get Outlook for iOS On Mon, Dec 19, 2016 at 9:49 PM +1100, "Tomasz Maruszak" <[email protected]> wrote: @socdream and @eByte23 did you integrate successfully with ADFS and this library (over SAML2.0 protocol)? What I can tell the library worked well with PingFederate as identity provider, now wondering about ADFS. My use case requires to use SAML2 protocol and ADFS is one of the target IdP. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.