Web site authentication takes backstage to email authentication due to new initiatives using SIDF and other formats. A study conducted by Evans Data Corporation, “Spring 2005 Web Services/SOA Development Survey,” looks into how developers address authentication.
Evans identified Web services security as a “home-grown” enterprise, stating upto 23 percent of developers build their own authentication systems. The survey reports 22 percent use SSL (define), and only nine percent use SOAP (define) headers, both industry-standard protocols. One quarter respondents cite authentication as the largest problem in Web services security.
|What Will Your Web Services Primarily Use for Authentication?|
|Custom security token||20||4.9||5.7|
|HTTP auth XACML||20||4.9||5.7|
|RSA’s Clear Trust||3||0.7||0.9|
|Tivoli Access Manager||1||0.2||0.3|
|Source: Evans Data Corp., 2005|
Developing authentication for an enterprise site creates resource demands, and finding IT professionals versed in Web services development is an issue for 19 percent of respondents.
“The value of the Web service, a standardized applications unit, are realized when the component is available for reuse within or outside the enterprise. The developers only need to build and test this application one time,” said Joe McKendrick, an analyst at Evans Data Corporation. ” The ROI will be realized when these services are reused on a frequent basis across enterprises. “
Recommendations in the report suggest businesses share Web service resources, yet 55 percent of respondents say they don’t share, or only share with one other business unit within their company. Only six and a half percent share across more than 20 businesses.