000 02314nam a22003855i 4500
001 978-1-4302-5783-7
003 DE-He213
005 20140220082801.0
007 cr nn 008mamaa
008 130510s2013 xxu| s |||| 0|eng d
020 _a9781430257837
_9978-1-4302-5783-7
024 7 _a10.1007/978-1-4302-5783-7
_2doi
050 4 _aQA75.5-76.95
072 7 _aUY
_2bicssc
072 7 _aCOM014000
_2bisacsh
082 0 4 _a004
_223
100 1 _aLakshmiraghavan, Badrinarayanan.
_eauthor.
245 1 0 _aPro ASP.NET Web API Security
_h[electronic resource] :
_bSecuring ASP.NET Web API /
_cby Badrinarayanan Lakshmiraghavan.
264 1 _aBerkeley, CA :
_bApress :
_bImprint: Apress,
_c2013.
300 _aXVII, 416 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
520 _aASP.NET Web API is a key part of ASP.NET MVC 4 and the platform of choice for building RESTful services that can be accessed by a wide range of devices. Everything from JavaScript libraries to RIA plugins, RFID readers to smart phones can consume your services using platform-agnostic HTTP. With such wide accessibility, securing your code effectively needs to be a top priority. You will quickly find that the WCF security protocols you’re familiar with from .NET are less suitable than they once were in this new environment, proving themselves cumbersome and limited in terms of the standards they can work with. Fortunately, ASP.NET Web API provides a simple, robust security solution of its own that fits neatly within the ASP.NET MVC programming model and secures your code without the need for SOAP, meaning that there is no limit to the range of devices that it can work with – if it can understand HTTP, then it can be secured by Web API. These SOAP-less security techniques are the focus of this book.
650 0 _aComputer science.
650 1 4 _aComputer Science.
650 2 4 _aComputer Science, general.
710 2 _aSpringerLink (Online service)
773 0 _tSpringer eBooks
776 0 8 _iPrinted edition:
_z9781430257820
856 4 0 _uhttp://dx.doi.org/10.1007/978-1-4302-5783-7
912 _aZDB-2-CWD
999 _c94347
_d94347