1 Articles match "Issuer","WCF"

19 Articles match "Issuer","WCF"

• The Best from DevelopMentor

  MORE

• Certificate Validation and Setting up Service Bus 1.0 Beta for Windows Server
  
  Certificate validation has a number of steps to it for a certificate to be considered valid: The issuer of the cert must be trusted. In fact the issuer of the issuer must also be trusted. In fact the issuer of the issuer of the issuer must be trusted. In other words, when a certificate is validated all certificates in the chain of issuers must be trusted back to a trusted root CA (normally bodies like Verisign or your corporate certificate server). Microsoft recently announced the beta of Service Bus 1.0 for Windows Server. So why this blog post?
  DevelopMentor Courses - Wednesday, July 25, 2012
  READ MORE
• Token based Authentication for WCF HTTP/REST Services: Authentication
  
  This post shows some of the implementation techniques for adding token and claims based security to HTTP/REST services written with WCF. Should work with WCF web programming model either self-host or IIS hosted. In WCF the main extensibility point for this kind of security work is the ServiceAuthorizationManager. WCF error handler takes care of turning “access denied” faults into 401 status codes and a message inspector adds the registered authentication schemes to the outgoing WWW-Authenticate header when a 401 occurs. Disclaimer. Goals and requirements.
  www.leastprivilege.com - Tuesday, November 15, 2011
  READ MORE
• Thinktecture.IdentityModel: WIF Support for WCF REST Services and OData
  
  The latest drop of Thinktecture.IdentityModel includes plumbing and support for WIF, claims and tokens for WCF REST services and Data Server (aka OData). Cibrax has an alternative implementation that uses the WCF Rest Starter Kit. Features include: generic plumbing for all WebServiceHost derived WCF services. based solely on native WCF extensibility points (and WIF). This post walks you through the setup of an OData / WCF DataServices endpoint with token authentication and claims support. support for SAML and SWT tokens. Setting up the Data Service. Claims. {.
  www.leastprivilege.com - Wednesday, May 5, 2010
  READ MORE
• WIF, ADFS 2 and WCF–Part 6: Chaining multiple Token Services
  
  So far we looked at the (simpler) scenario where a client acquires a token from an identity provider and uses that for authentication against a relying party WCF service. As we discussed in part 4 , the bindings must be nested for WCF to unwind the token call-stack. Using the manual approach you have full control over that parameter and you can simply use the R-STS issuer URI. Another issue you will run into is, that ADFS does only accepts its configured issuer URI as a known realm by default. See the previous posts first. var factory = new WSTrustChannelFactory (.
  www.leastprivilege.com - Thursday, October 28, 2010
  READ MORE
• WIF, ADFS 2 and WCF–Part 2: The Service
  
  OK – so let’s first start with a simple WCF service and connect that to ADFS 2 for authentication. ClaimType = c.ClaimType, Value = c.Value, Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer. }).ToList(); Next is the WCF configuration – let’s have a look step by step. name = " ADFS " /> The last step (promised) is to add the allowed audience URIs to the configuration – WCF clients use (by default – and we’ll come back to this) the endpoint address of the service: OK – that’s it – now we have a basic WCF service that uses ADFS 2 for authentication.
  www.leastprivilege.com - Monday, October 11, 2010
  READ MORE
• WIF Configuration – Part 1: ServiceConfiguration
  
  for token handlers, issuer name registries or claims authorization). This is useful when you build your own integration, but for WCF and ASP.NET there is already an infrastructure in place. In WCF you wire up WIF with by calling FederatedServiceCredentials.ConfigureServiceHost(…). Tags: ASP.NET IdentityModel WCF WIF supports a flexible configuration system and various ways to programmatically interact with that configuration. This flexibility comes in two ways: Named configuration elements that you can selectively load (service & token handler configuration).
  www.leastprivilege.com - Tuesday, December 22, 2009
  READ MORE
• Using IdentityModel: Windows and X509Certificate Claim Sets
  
  WCF uses these classes to create claim sets for Windows/certificate clients. The issuer of this claim set will be always ClaimSet.Windows. The X509CertificateClaimSet converts some of the attributes of an X509 certificate (and its issuers) to a claim set. The claim set issuer chain reflects the certificate issuer chain (by calling X509Chain.Build ): When the cert is self issued, the issuer will point to itself. When the issuing cert is available, the issuer will be a X509CertificateClaimSet. But you can also use them "standalone".
  www.leastprivilege.com - Sunday, February 24, 2008
  READ MORE