From fde9165161e28e1f9d03dc41ee7d3edc8672f16a Mon Sep 17 00:00:00 2001 From: David Anderson Date: Sun, 31 Mar 2024 15:49:12 -0700 Subject: [PATCH] Updated SimpleAttach (markdown) --- SimpleAttach.md | 20 -------------------- 1 file changed, 20 deletions(-) diff --git a/SimpleAttach.md b/SimpleAttach.md index 31fc4ef..bd30637 100644 --- a/SimpleAttach.md +++ b/SimpleAttach.md @@ -103,23 +103,3 @@ When the client startup it, it looks for this file. If found, does a "lookup account token" RPC to the project, obtaining the user name and a weak authenticator. It attaches to the project using this authenticator. - -## Auto-attach from another web site - -Suppose you want to make a web site that acts as a "front end" -to a BOINC project or account manager. -Users create accounts on the front-end site, -and they end up computing for the back-end projector AM. -But you want their interaction to be entirely with the front-end site. - -Here's how to do this: - -* The front-end system must obtain an "RPC key" from the back-end system. -* When a user creates an account on the front-end site, it uses the [create_account RPC](WebRpc#create_account) to create a corresponding account on the back-end site, and it records the authenticator of this account. -* The front-end site has a Download page. This page uses the [download_software()](WebRpc#download) RPC to get info from the back-end system that is used to create Download buttons which auto-attach the user to the back-end system. - -To see how this works, look at the example code in -[web_rpc_api.inc](https://github.com/BOINC/boinc/blob/dpa_download_info/html/inc/web_rpc_api.inc). -The download_software() RPC is described [here](WebRpc#download). - -Note: this is currently deployed only on the Science United account manager.