Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
tbd:db_unix [2009/04/28 15:41] janakj |
tbd:db_unix [2013/04/17 11:53] (current) henningw old revision restored |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Integration With UNIX/Linux User Database ====== | ====== Integration With UNIX/Linux User Database ====== | ||
| + | **Contacts**: | ||
| + | |||
| + | ===== Abstract ===== | ||
| The goal of this work is to develop an extension module for sip-router that | The goal of this work is to develop an extension module for sip-router that | ||
| - | will provide support for authentication, | + | will provide support for authentication, |
| - | UNIX way, that is ''/ | + | UNIX way**, that is ''/ |
| user's home directory. With this module loaded the sip-router server will be | user's home directory. With this module loaded the sip-router server will be | ||
| - | able to integrate with services and databases commonly available in UNIX | + | able to integrate with name services and databases commonly available in UNIX-like |
| systems. | systems. | ||
| - | Every non-trivial sip-router requires a database server to store all kinds of | + | ===== State of the Art ===== |
| - | data particular to the operation of the SIP server. All users' data, such as | + | Every non-trivial sip-router |
| + | of data particular to the operation of the SIP server. All users' data, such as | ||
| authentication usernames, passwords and user location contacts, is then stored | authentication usernames, passwords and user location contacts, is then stored | ||
| in the database. The administrator usually needs to populate the database with | in the database. The administrator usually needs to populate the database with | ||
| Line 33: | Line 37: | ||
| provisioning tools and maintenance. | provisioning tools and maintenance. | ||
| + | ===== Goals ===== | ||
| The aim of this work is to develop an extension module for sip-router which | The aim of this work is to develop an extension module for sip-router which | ||
| will interface to the database abstraction layer in sip-router on one side to | will interface to the database abstraction layer in sip-router on one side to | ||
| Line 41: | Line 46: | ||
| Modules) system for authorization, | Modules) system for authorization, | ||
| - | ===== Required features | + | ==== Required features ==== |
| - | ==== Version 1 (strawman) | + | === Version 1 (strawman) === |
| * Use ''/ | * Use ''/ | ||
| * Digest authentication password stored in '' | * Digest authentication password stored in '' | ||
| Line 48: | Line 53: | ||
| * Authorization to use the service using ''/ | * Authorization to use the service using ''/ | ||
| - | ==== Version 2 (deluxe) | + | === Version 2 (deluxe) === |
| * PAM-enabled authorization | * PAM-enabled authorization | ||
| * Selected configuration for a user (a set of name-value pairs) can be stored in a plain-text file in '' | * Selected configuration for a user (a set of name-value pairs) can be stored in a plain-text file in '' | ||
| Line 55: | Line 60: | ||
| * Tool to administer the digest password in '' | * Tool to administer the digest password in '' | ||
| - | ===== Overview of operation | + | ===== Overview of Operation |
| The administator of a Linux host installs the sip-router. The sip-router comes | The administator of a Linux host installs the sip-router. The sip-router comes | ||
| with a default configuration file with all important features, such as digest | with a default configuration file with all important features, such as digest | ||
| Line 103: | Line 107: | ||
| configuration by editing '' | configuration by editing '' | ||
| + | ===== Reading List ===== | ||
| + | * [[http:// | ||
| + | * [[http:// | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | | ||
