Category Archives: networking

MS is back !

During the recent past the IT industry has seen some innovative innovations 🙂

IBMSecond Life (?) / IBM’s Cell Processor’s.

AppleiPhone / iPod.

Microsoft – ? (Vista, Zune – it’s different story that they do not work together)

Google – ?

(Please help me fill in these question marks)

It seemed that Microsoft was falling behind in finding something ‘new’. But I was wrong. It seemed to be the silence before the storm.

MS is back! Back with a BANG.

Touch Screen Technology has finally evolved / matured .

Just have a look @ this from Microsoft. It’s called Microsoft Surface.

(Read an article from TechCrunch called Microsoft Announces Surface Computer. The comments to this post @ TechCrunch are worth reading.)

Imagine a Virtual World (Second Life) with Microsoft Surface and being able to use iPhone in Virtual Life and getting it synchronized with an iPod in First Life!

Playing Age of Empires on Surface with a Cell Processor. All Game for it.

This technology would further enhance the user experience, taking it to a new level. Imagine a porn movie on a Microsoft Surface in First Life 😉 .

 

WS – TRUST

Concept

SOAP-MSG protected by WS-Security has 3 possible issues in regards to SECURITY TOKEN.

  • Security Token format incompatibility
  • Security Token trust
  • Namespace differences

WS-TRUST addresses these issues by introducing a STS (Secure Token Service).

Example Scenario: –

In order to secure a communication between two parties, the two parties must exchange security credentials (either directly or indirectly). However, each party needs to determine if they can “trust” the asserted credentials of the other party. WS-TRUST specification defines extensions to [WS-Security] that provide:

· Methods for issuing, renewing, and validating security tokens.

· Ways to establish, assess the presence of, and broker trust relationships

The goal of WS-Trust is to enable applications to construct trusted [SOAP] message exchanges. This trust is represented through the exchange and brokering of security tokens. This specification provides a protocol agnostic way to issue, renew, and validate these security tokens.

Implementation Strategy

Web Services Trust Model

TOOLS

1. IBM® Tivoli® Federated Identity Manager provides an implementation of the WS-Trust specification. It acts as a STS.

2. Security Token Generation can be done by configuring WAS

Example:

1. Client understands X.509 certificates only.

2. Service understands SAML only.

  1. SOAP Gateway recognizes that it must map to SAML, so it contacts the STS.
  2. The STS sends back the token in the requested format.
  3. The gateway formats and sends the message for the service.
Summary

WS-TRUST addresses the security token needs of SOAP messages as

1. Format: An STS is used to exchange tokens into formats understandable by recipients.

2. Trust: The STS issues signed tokens forming the basis of trust for entities with which it has formed a trust relationship.

3. Namespace: The STS will return tokens in appropriate syntax for the recipient.

Discussions welcome. The doc. was created for introductory purposes.

Anything you wish should be added / removed / changed ? plz. let me know.

the doc. can be found here :  WS – TRUST

Technorati tags: , , , , , , , ,

WS – Specifications

While searching for materials on WebService Trust, I came across this presentation, which acts as a good introduction to the concept.

And also the following figure, which summarizes the web services specification stack.

WS-Secure Conversation : How to manage and authenticate message exchanges between parties including security context exchange and establishing and deriving session keys.

WS-Federation : How to manage and broker the trust relationships in a heterogeneous, federated environment including support for federated identities

WS-Authorization : How to manage authorization data and authorization policies.

WS-Policy : The capabilities and constraints of security and other business policies on intermediaries and endpoints (for example, required security tokens, supported encryption algorithms and privacy rules).

WS-Trust : A framework for trust models that enables Web services to securely

interoperate.

WS-Privacy : A model for how Web services and requesters state subject privacy

preferences and organizational privacy practice statements.

WS-Security : How to attach signature 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 (an encryption system developed at MIT), to messages.

Technorati tags: , , , , , , , , ,

<XML> </xml>

I came across a good article on xml being case sensitive.

A good article on

  1. KISS : Keep it Simple Stupid here.
  2. xKISS : XML Key Information Service Specification here.
  3. and what more are you looking for 😉 .

It’s something as simple as xml because of which SOA is possible ?

what do you think ?

 

Technorati tags: , , , , ,

Social Networking

It’s everywhere – – Web 2.0
Kathy Sierra’s comments . .
And. . how can one forget the Second Life ! here
Some new tools Plazer !

A very good blog Andy Piper

An interesting site TechnoratI
My blog stats @ technorati