Autodesk 15606-011408-9330 User Guide - Page 81

Access Keys Versus User IDs and Passwords, Users/Groups/Passwords, Access Keys, Time Period, End-User

Page 81 highlights

Access Keys Versus User IDs and Passwords Access keys are passwords that the author of a map embeds in the definition of the map layer. Each time the map layer requests map data, Autodesk MapGuide Server verifies the embedded access key against the list of valid access keys for the resource before fulfilling the request. Because this process takes place automatically and invisibly every time the map layer requests data, access keys are a convenient way to provide greater resource security with no impact on the user. Additionally, access keys can be preset to be valid for only a certain period of time, adding an additional level of control. User passwords require the user to enter a valid user name and password at the first request of map data from Autodesk MapGuide Server. Like the typical Web server security model, the user name and password are required only once for each layer that uses the restricted resource, providing a high level of security without unnecessary impact on the user. Together, access keys and user passwords provide a great deal of flexibility in solving security problems over a variety of Internet/intranet implementations. The following table provides a summary of the differences between the two security methods: Time Period End-User Interaction Implementation Authorization Frequency Users/Groups/Passwords Active until deleted. Access Keys Preset time periods. User must enter correct name and password. No end-user interaction. Use Autodesk MapGuide Server Admin to enter and maintain users, groups, and passwords. Use Autodesk MapGuide Author to enter access keys in MWFs; use Autodesk MapGuide Server Admin to link access keys to resources at the server level. Checked once per resource per layer request (until the user exits the current browser session). Checked by Autodesk MapGuide Server for every layer request. Managing Server Security | 81

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 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
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204

Managing Server Security
|
81
Access Keys Versus User IDs and Passwords
Access keys are passwords that the author of a map embeds in the definition
of the map layer. Each time the map layer requests map data, Autodesk
MapGuide Server verifies the embedded access key against the list of valid
access keys for the resource before fulfilling the request. Because this process
takes place automatically and invisibly every time the map layer requests
data, access keys are a convenient way to provide greater resource security
with no impact on the user. Additionally, access keys can be preset to be valid
for only a certain period of time, adding an additional level of control.
User passwords require the user to enter a valid user name and password at
the first request of map data from Autodesk MapGuide Server. Like the
typical Web server security model, the user name and password are required
only once for each layer that uses the restricted resource, providing a high
level of security without unnecessary impact on the user.
Together, access keys and user passwords provide a great deal of flexibility
in solving security problems over a variety of Internet/intranet implementa-
tions.
The following table provides a summary of the differences between the two
security methods:
Users/Groups/Passwords
Access Keys
Time Period
Active until deleted.
Preset time periods.
End-User
Interaction
User must enter correct name
and password.
No end-user interaction.
Implementa-
tion
Use Autodesk MapGuide Server
Admin to enter and maintain
users, groups, and passwords.
Use Autodesk MapGuide
Author to enter access keys in
MWFs; use Autodesk
MapGuide Server Admin to
link access keys to resources
at the server level.
Authorization
Frequency
Checked once per resource per
layer request (until the user
exits the current browser
session).
Checked by Autodesk
MapGuide Server for every
layer request.