StaticGround

In new York

So my JetBlue flight from Oakland to NY was cancelled due to weather.
So, day one of my vacation will be spent haggling with agents at
airport ticket counters. I was also planning to visit Paris, but I have no time
for that now. 

I was in total shock when I arrived at the airport and found out that my flight was cancelled.  There were two later JetBlue flights to NY, but they were delayed.  The JetBlue person was nice enough to try to find me a JetBlue flight that would get me to NY in time for my flight to London, but every flight was sold out.  So I sat and waited for the JetBlue agent to find me another flight for 3 hours while people around me checked in their bags going to NY.  He called my other airline and tried to see if they would change my reservation, but they said that I would either have to fly standby, or pay $1500 for a ticket.  So I agreed to go standby to London, and the JetBlue agent refunded my ticket, and purchased another ticket for me on another airline.  

 

From the BEA site: WS Security

"

Web Services Security Specifications

• WS-Security describes how to attach signature and encryption headers to SOAP messages. In addition, it describes how to attach security tokens, including binary security tokens such as X.509 certificates and Kerberos tickets, to messages.
  
• WS-Policy represents a set of specifications that describe the capabilities and constraints of the security (and other business) policies on intermediaries and endpoints (e.g. required security tokens, supported encryption algorithms, privacy rules) and how to associate policies with services and endpoints.
  
• WS-Trust describes a framework for trust models that enables Web services to securely interoperate by requesting, issuing, and exchanging security tokens.
  
• WS-Privacy will describe a model for how Web services and requestors state privacy preferences and organizational privacy practice statements.
  
• WS-SecureConversation describes how to manage and authenticate message exchanges between parties, including security context exchanges and establishing and deriving session keys.
  
• WS-Federation describes how to manage and broker the trust relationships in a heterogeneous federated environment, including support for federated identities, sharing of attributes, and management of pseudonyms.
  
• WS-Authorization will describe how to manage authorization data and authorization policies.
  

Additionally, several other key Web services specifications complete the foundation layer of specifications:

• WS-Addressing describes how to specify identification and addressing information for messages.
  
• WS-MetadataExchange describes how to exchange metadata such as WS-Policy information and WSDL between services and endpoints.
  
• WS-ReliableMessaging describes how to ensure reliable delivery of messages in the presence of unreliable networks.
  
• WS-Transactions and WS-Coordination describe how to enable transacted operations as part of Web service message exchanges.
  

The combination of the specifications above and interoperability profiles will enable customers to easily build interoperable secure reliable transacted Web services that integrate within and across federations by composing federation and security specifications with other Web services specifications. "

Using the System.Threading and System.Security.Principal namespaces, you can obtain the identity of the user associated with the current thread:

AppDomain.CurrentDomain.SetPrincipalPolicy(PrincipalPolicy.WindowsPrincipal);



IPrincipal wp = Thread.CurrentPrincipal;

IIdentity id = wp.Identity;



string authType = id.AuthenticationType;

string isAuth = id.IsAuthenticated.ToString();

string name = id.Name;