While exploring
this issue in the section ???HTTPS, Authentication, and
Digital Identity,??? we highlighted the fact that the most notable
consequence of such a shortcoming is that credentials handling
is currently a responsibility of the application developer.
We have seen how this simple fact promotes strong differentiation
in the feature sets of libraries and components; in this section,
we discuss the impact it has on the interactions with the
end user. We also consider user perception in general and how
SAML tends to
leverage business
relationships that
usually do not
apply to single
users
Convincing everybody
to standardize
on a single technology
is very dif?¬?cult
80 The Problem
the feeling of not being in control of the situation affects
people??™s trust in online systems in general.
In the section ???HTTP and HTTPS: The King Is Naked??? we have
seen in extreme synthesis how the Internet works: You type an
address, and the browser takes care of requesting the corresponding
page and rendering it. URLs are one of the few indications
of ???where??? the user is (that is, where the page currently rendered
in the browser comes from). Actually, there??™s often no need to
type addresses.
Pages:
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151