| | 174 | ==== Cookieless Installs ==== |
| | 175 | |
| | 176 | For unsupported browsers or projects with custom installers, we will pass the needed information |
| | 177 | by renaming the installer to include the additional information. |
| | 178 | |
| | 179 | Executable parameters are as follows: |
| | 180 | |
| | 181 | '''amu''': the master URL |
| | 182 | '''an''': the project name |
| | 183 | '''aa''': the user authenticator |
| | 184 | '''asc''': the setup cookie |
| | 185 | |
| | 186 | Usage Rules: |
| | 187 | |
| | 188 | * Each parameter is broken up into name/value pairs |
| | 189 | * Each name/value pair is separated by an underscore |
| | 190 | * Each value is base64 encoded |
| | 191 | |
| | 192 | Note: Using the setup cookie is more desirable than storing the authenticator as part of the |
| | 193 | executable name. Setup cookies are created by the project server and expire after a given |
| | 194 | period of time. During the manager's attach process, it'll use the lookup account RPC to |
| | 195 | convert the setup cookie into the user's weak authenticator. |
| | 196 | |