Modify Your Results

As systems have become interconnected and more complicated, programmers needed ways to identify parties across multiple computers. One way to do this was for the parties that used applications on one computer to authenticate to the applications (and/or operating systems) that ran on the other computers. This mechanism is still widely used-for example, when logging on to a great number of Web sites. However, this approach becomes unmanageable when you have many co-operating systems (as is the case, for example, in the enterprise). Therefore, specialized services were invented that would register and authenticate users, and subsequently provide claims about them to interested applications. Some well-known examples are NTLM, Kerberos, Public Key Infrastructure (PKI), and the Security Assertion Markup Language (SAML). Most enterprise applications need some basic user security features. At a minimum, they need to authenticate their users, and many also need to authorize access to certain features so that only privileged users can get to them. Some apps must go further and audit what the user does. On Windows®, these features are built into the operating system and are usually quite easy to integrate into an application. By taking advantage of Windows integrated authentication, you don't have to invent your own authentication protocol or manage a user database. By using access control lists (ACLs), impersonation, and features such as groups, you can implement authorization with very little code. Indeed, this advice applies no matter which OS you are using. It's almost always a better idea to integrate closely with the security features in your OS rather than reinventing those features yourself. But what happens when you want to extend reach to users who don't happen to have Windows accounts? What about users who aren't running Windows at all? More and more applications need this type of reach, which seems to fly in the face of traditional advice. This book gives you enough information to evaluate claims-based identity as a possible option when you're planning a new application or making changes to an existing one. It is intended for any architect, developer, or information technology (IT) professional who designs, builds, or operates Web applications and services that require identity information about their users.

Get hands-on guidance designed to help you put the newest .NET Framework component- Windows Identity Foundation, the identity and access logic for all on-premises and cloud development- to work.

Copyright:
2001

Showing 1 through 2 of 2 results

Help

Select your format based upon: 1) how you want to read your book, and
2) compatibility with your reading tool. To learn more about using
Bookshare with your device, visit the "Using
Bookshare" page in the Help Center.

Here is an overview of the specialized formats that Bookshare
offers its members with links that go to the Help Center for more
information.

Bookshare Web
Reader - a customized reading tool for Bookshare members offering all
the features of DAISY with a single click of the "Read Now" link.

DAISY
(Digital Accessible Information System) - a digital book file format.
DAISY books from Bookshare are DAISY 3.0 text files that work with
just about every type of access technology that reads text. Books that
contain images will have the download option of ‘DAISY Text with
Images’.

MP3 (Mpeg audio
layer 3) - Provides audio only with no text. These books are created
with a text-to-speech engine and spoken by Kendra, a high quality
synthetic voice from Ivona. Any device that supports MP3 playback is
compatible.

DAISY Audio
- Similar to the Daisy 3.0 option above; however, this option uses MP3
files created with our text-to-speech engine that utilizes Ivona's
Kendra voice. This format will work with Daisy Audio compatible
players such as Victor Reader Stream and Read2Go.