Thanks for doing these. Perfect timing for me! I’m adding authentication & authorisation to my trusted WPF applications and have watched the part 1 last week. Great content. Is there much changes required to adapt what’s in your course to .NET4 and WIF?
Are there any plans for follow up courses dealing with active (non-browser) clients, trusted applications or even the self-hosted Thinktecture identity server?
THANK YOU!!! Your pluralsight courses are awesome. Any ETA? Will you cover webHttpBinding (WCF REST) with OAuth2 and SWT? How about federated authentication with ACS?
We have a identity provider which supports SAML 2P Protocol. As per our understanding, ThinkTecture doesn’t support SAML 2P. In order to communicate with SAML 2P, Can we proceed to alter the federation metadata of Thinktecture which understands by my identity provider. Is it a right way to do or any other approach available. If we change the metadata of thinktecture, is it will affect the other providers support?
Hi,
Thanks for your reply. We have a requirement to support SAML2P in thinktecture .We are planning to extend Thinktecture to support SAML2P. As per the understanding, We need to generate SAML2P based metadata and implement the protocol in TT. We are using hrd endpoint and added SAML2P supported in thinktecture Identity provider configuration. Do we need to extend HRDController.cs to process SAML2P request. Then how user credentials will be passed by using hrd select screen? For SAML 2P support, we are in the right track or not.Please guide us.
Thanks for doing these. Perfect timing for me! I’m adding authentication & authorisation to my trusted WPF applications and have watched the part 1 last week. Great content. Is there much changes required to adapt what’s in your course to .NET4 and WIF?
Well – there are a lot of small changes (everywhere). So yes.
Are there any plans for follow up courses dealing with active (non-browser) clients, trusted applications or even the self-hosted Thinktecture identity server?
Yes. I will do a WCF one as well. Recording right now.
THANK YOU!!! Your pluralsight courses are awesome. Any ETA? Will you cover webHttpBinding (WCF REST) with OAuth2 and SWT? How about federated authentication with ACS?
No.
I will cover WCF + SOAP. I will do a Web API one later.
ok :( Will be looking forward to it :) Pluralsight has got another user because of your courses ;)
Thanks again for the amazing videos.
Hi Dominick,
We have a identity provider which supports SAML 2P Protocol. As per our understanding, ThinkTecture doesn’t support SAML 2P. In order to communicate with SAML 2P, Can we proceed to alter the federation metadata of Thinktecture which understands by my identity provider. Is it a right way to do or any other approach available. If we change the metadata of thinktecture, is it will affect the other providers support?
Simply changing the metadata document will not teach IdSrv to speak SAMLp. The protocol is not implemented.
Hi,
Thanks for your reply. We have a requirement to support SAML2P in thinktecture .We are planning to extend Thinktecture to support SAML2P. As per the understanding, We need to generate SAML2P based metadata and implement the protocol in TT. We are using hrd endpoint and added SAML2P supported in thinktecture Identity provider configuration. Do we need to extend HRDController.cs to process SAML2P request. Then how user credentials will be passed by using hrd select screen? For SAML 2P support, we are in the right track or not.Please guide us.
How did you add SAML2p support?
It would be a non-trivial undertaking to implement SAML2p in IdSrv (especially when you want to implement HRD).
use office@thinktecture.com.