1 / 5

SIP Authentication using CHAP-Password

SIP Authentication using CHAP-Password. draft-byerly-sip-radius-00.txt. Bryan J. Byerly David Williams. Problem and Objectives. Problem HTTP-Digest user authentication is not compatible with deployed backend Radius servers.

christmas
Download Presentation

SIP Authentication using CHAP-Password

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIP Authentication using CHAP-Password draft-byerly-sip-radius-00.txt Bryan J. Byerly David Williams

  2. Problem and Objectives • Problem • HTTP-Digest user authentication is not compatible with deployed backend Radius servers. • SIP user authentication (RFC2617) and Radius (RFC 2138) user authentication run MD5 over differently formatted messages. • Objective • Provide mechanism to allow authentication of users using deployed Radius servers. • Advantageous to ISPs deploying SIP voice service to PPP customers • Approaches • Extend SIP to support CHAP-Password • Extend Radius to support HTTP-Digest

  3. Comparison of hash formats • CHAP-Password: MD5 • MD5(seqnum, user-password, nonce) • HTTP-Digest: MD5 • MD5(unq(username-value) “:” unq(realm-value) “:” password) • HTTP-Digest: MD5-sess • MD5(unq(username-value) “:” unq(realm-value) “:” password “:” unq(nonce-value) “:” unq(cnonce-value))

  4. 407 Proxy Authorization Required Proxy-Authenticate: CHAP-Password ;algorithm="MD5" ;id=0 ;nonce="cccccccccccccccccccccccccccccccc" SIP client SIP proxy RADIUS server Proxy-Authorization: CHAP-Password ;username="byerly" ;algorithm="MD5" ;id=0 ;nonce="cccccccccccccccccccccccccccccccc" ;response="dddddddddddddddddddddddddddddddd" INVITE CHAP-Password=(dddddddddddddddddddddddddddddddd) Access-Request INVITE Access-Accept INVITE SIP User Authentication using Radius backend

  5. Future • Remaining issues • Multiple Proxy-Authorization headers (semicolon vs. comma separated tags) • Is additional complexity of Mahler draft necessary? • Reflection attack in trusted side of network • Proposed next steps • SIP WG item • Standards track

More Related