METHOD AND SYSTEM FOR INTEGRATING SECURITY MECHANISMS INTO SESSION INITIATION PROTOCOL REQUEST MESSAGES FOR CLIENT-PROXY AUTHENTICATION

• US 20080022383A1
• Filed: 06/04/2007
• Published: 01/24/2008
• Est. Priority Date: 06/14/2001
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Bobde, Nikhil, Han, Mu, Demirtjis, Ann
• Granted Patent: US 7,770,007 B2
• Time in Patent Office: Days
• US Class Current: 726/10
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/0869 for achieving mutual authentication cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/205 involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved negotiation of communication capabilities H04L69/24
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

A method and system is provided to integrate the Kerberos security mechanism into the message flow of the signaling operation under the Session Initiation Protocol to allow a SIP client and a SIP proxy to authenticate each other. When the SIP proxy receives an request message, such an INVITE request, from the SIP client, it responds with a challenge message indicating that authentication based on Kerberos is required. In response, the SIP client sends a second request message with a proxy authorization header containing authentication data, including a Kerberos server ticket for the Proxy, to allow the proxy to authenticate the client'"'"'s user.

Claims

1-28. -28. (canceled)

29. A method of a Session Initiation Protocol (“

SIP”

) client for providing mutual authentication between the SIP client and a SIP proxy, comprising;

sending to the SIP proxy a first request;

receiving from the SIP proxy a first challenge to the first request that includes a SIP proxy security context;

in response to the SIP client receiving the first challenge,

obtaining from a distribution center a session key of the SIP proxy and a server ticket, the server ticket encrypted with a key of the SIP proxy and including authentication data of the SIP client; and

sending to the SIP proxy a second request signed using the session key and including the server ticket and a security context based on the SIP proxy security context;

receiving from the SIP proxy a first response to the second request; and

verifying that the first response was signed using the session key to authenticate the SIP proxy.

30. The method of claim 29 further comprising signing a subsequent request sent to the SIP proxy with the session key.

31. The method of claim 30 further comprising receiving a second challenge to the second request from the SIP proxy;

in response to receiving the second challenge, obtaining from the distribution center a new session key and a new server ticket; and

sending to the SIP proxy a third request signed using the new session key and including the new server ticket.

32. The method of claim 29 wherein a first request is a member of a group comprising an invite request, a register request, a message request, a subscribe request, a notify request, and a service request.

33. The method of claim 29 further comprising the SIP proxy, upon receiving the second request,

the SIP proxy receiving the second request;

in response to receiving the second request, the SIP proxy decrypting the server ticket based on the key of the SIP proxy;

the SIP proxy forwarding the second request to a server when the authentication data in the decrypted server ticket indicates that the SIP client is authentic, the security context included in the second request matches the SIP proxy security context, and the second request is signed by the session key;

in response to receiving from the server a second response to the second request, the SIP proxy generating the first response by signing with the session key and forwarding the first response to the SIP client.

34. The method of claim 29 further comprising:

the SIP proxy receiving from the SIP client the first request;

in response to receiving the first request, the SIP proxy creating the session key with the distribution center; and

the SIP proxy sending to the SIP client the first challenge that includes the SIP proxy security context.

35. The method of claim 29 wherein the server ticket includes a copy of the session key.

36. A computer-readable medium having computer executable instructions for controlling a Session Initiation Protocol (“

SIP”

) proxy to provide mutual authentication with a SIP client, by a method comprising;

receiving a first request from the SIP client;

in response to the first request, sending to the SIP client a first challenge that includes a SIP proxy security context;

determining a session key of the SIP proxy with a distribution center;

receiving a second request from the SIP client that includes a server ticket;

in response to the second request, decrypting the server ticket of the second request using a key of the SIP proxy; and

when authentication data of the SIP client in the decrypted server ticket indicates that the SIP client is authentic, a security context included in the second request matches the SIP proxy security context, and the second request is signed by the session key, signing a response with the session key to establish authentication of the response and forwarding the signed response to the SIP client.

37. The computer-readable medium of claim 36 wherein determining a session key of the SIP proxy with the distribution center includes the SIP proxy creating the session key and providing the session key to the distribution center.

38. The computer-readable medium of claim 36 wherein the server ticket includes the session key.

39. The computer-readable medium of claim 36 further comprising:

the SIP client sending the first request to the SIP proxy;

in response to receiving the challenge, the SIP client determining the session key of the SIP proxy with the distribution center;

in response to receiving the challenge, the SIP client obtaining from the distribution center the server ticket encrypted with the key of the SIP proxy, the server ticket including authentication data of the SIP client;

the SIP client generating the second request by signing the server ticket encrypted with the key of the SIP proxy, and signing the SIP proxy security context with the session key;

the SIP client sending to the SIP proxy the second request; and

in response to receiving the signed response, the SIP client verifying that the response was signed using the session key to authenticate the SIP proxy.

40. The computer-readable medium of claim 39 wherein the key of the SIP proxy is a long-term key of the SIP proxy, and wherein the SIP proxy obtaining from the distribution center includes obtaining the server ticket encrypted with the long-term key of the SIP proxy.

41. The computer-readable medium of claim 39 further comprising the SIP client signing a subsequent message to the SIP proxy using the session key, and sending the signed subsequent message to the SIP proxy.

42. The computer-readable medium of claim 41 further comprising in response to receiving the subsequent message from the SIP client, the SIP proxy determining whether the subsequent message is signed using the session key.

43. The computer-readable medium of claim 39 further comprising in response to receiving a subsequent challenge from the SIP proxy, the SIP client obtaining from the distribution center a new session key and a new server ticket and the SIP client sending to the SIP proxy a third request signed using the new session key and including the new server ticket.

44. The computer-readable medium of claim 43 further comprising in response to the security context being no longer valid,

the SIP proxy sending to the SIP client the subsequent challenge that includes a new SIP proxy security context;

and

the SIP proxy creating a new session key of the SIP proxy with the distribution center.

45. The computer-readable medium of claim 36 wherein the first request is a member of a group comprising an invite request, a register request, a message request, a subscribe request, a notify request, and a service request.

46. A computing system for providing mutual authentication between a Session Initiation Protocol (“

SIP”

) client and a SIP proxy, comprising;

a SIP client component that

sends a first request to the SIP proxy;

in response to receiving from the SIP proxy a challenge to the first request, the challenge including a SIP proxy security context, obtains from a distribution center a session key of the SIP proxy and a server ticket, the server ticket encrypted with a key of the SIP proxy and including authentication data of the SIP client;

sends to the SIP proxy a second request signed using the session key and that includes the server ticket and a security context based on the SIP proxy security context;

receives from the SIP proxy a response to the second request; and

authenticates the SIP proxy by verifying that the response was signed using the session key; and

a SIP proxy component that

upon receiving the first request from the SIP client,

sends to the SIP client the challenge that includes the SIP proxy security context; and

creates the session key with the distribution center;

upon receiving the second request from the SIP client,

decrypts the server ticket of the second request using the key of the SIP proxy; and

when authentication data of the SIP client in the decrypted server ticket indicates that the SIP client is authentic, the security context included in the second request matches the SIP proxy security context, and the second request is signed by the session key,

generates the response by signing with the session key to establish authentication of the response; and

sends the response to the SIP client.

47. The computer system of claim 46 wherein the SIP client component signs subsequent requests sent to the SIP proxy with the session key.

48. The computer system of claim 46 wherein the SIP client component further, when a subsequent challenge is received from the SIP proxy, obtains from the distribution center a new session key and sends to the SIP proxy a subsequent request signed using the new session key.