adfs3.0

SSO from ADAL in WPF Client to ADFS 3.0 on Windows Server 2012 R2

非 Y 不嫁゛ 提交于 2019-12-04 13:34:41
I am trying to write an WPF client which uses ADAL to authenticate against ADFS on a Windows Server 2012 R2. I have successfully implemented this using "Forms Authentication" where the user is prompted for the domain username and password. However, I want to take advantage of SSO and use the currently logged on domain user to authenticate against the ADFS. Unfortunately, I'm only getting an error message saying: This method overload is not supported by '< ADFS servername>' I have done a lot of searching, but find some of the information contradictive: This SO post about a Windows Store App

ADFS as OAuth2 provider / Authentication server possible?

好久不见. 提交于 2019-11-30 22:51:54
We want to setup ADFS 3.0 to enable OAuth2 based authentication. I have read lots of documentation, but am still unclear if this is supported. Can ADFS be used as an authorization server for oauth, or is oauth2 support in ADFS only meant to work as a client to another authorization server? Any help for setting up adfs as oauth provider/server is appreciated. in ADFS 2012R2 (aka ADFS 3.0), we only support the authorization grant flow. The only scenario is for public clients (say a mobile app on iOS/Android/Windows) to access a RESTful service and authorizing via JWT tokens. You can see this at

Implementing Office 365 single sign-on using custom authentication/claims provider in ADFS 3.0 (RE: AADSTS90019)

和自甴很熟 提交于 2019-11-29 17:34:47
I have a new Claims Provider Trust successfully configured in ADFS 3.0 that allows us to use a separate SAML IdP and let ADFS 3.0 be the SP. We now see "You are signed in" when we go through our SAML IdP. So this part works fine (SSO into ADFS 3.0). However, attempting to access Office 365 apps now returns the following error by at https://login.microsoftonline.com/login.srf : AADSTS90019: No tenant-identifying information found in either the request or implied by any provided credentials. Any ideas? Do I need to add a Relying Party Trust to get Office 365 to also trust our SAML-based Claims