Internet applications can become increasingly complex
when the code that is written to handle the business of
the application is written in a way that it depends on the
infrastructure around it. To change the technology that
the identity store is built on, signi?¬?cant changes in the
business logic occur because the API (application programming
interface) for one system is not the same for
another. When the application uses a token created by
the STS to carry the identity information, the application
is no longer tightly coupled to that speci?¬?c identity store
or to its APIs. And, as a bonus, application developers
are freed from the complexity of understanding the identity
store and can use the tokens with much less effort.
Identity information may be consolidated from multiple
sources.
In some situations, the information that a system needs
about an individual is not in one database or even
hosted in the same facility. As an alternative to creating
an identity store (which may involve replicating the data
from other sources), an STS can accumulate the data and
consolidate it all into a single token that the application
can consume. The STS may even communicate outside
the organization, streamlining the process for accessing
external databases.
Pages:
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468