Is there some documentation that outlines the relationship and communication between the authentication mechanisms of BAM and BOINC projects?

It's a little unclear to me how BAM manages the hosts (if at all) of systems that are signed up under different project userids with multiple projects and with the same user id (same as BAM) but different passwords.

For instance.

Lets say I have 10 systems. All are running BOINC with two projects and have been signed up under 10 different userids. Each userid/pw is different for each project on each system. A systems administrator for the organization joins each system to his BAM account and can see them listed in his host table (along with his own personal BOINC attached computers).

The systems admin wants to add more systems and more users. If he uses BAM to manage new systems will the new systems by default join his personal accounts in the projects he has chosen (in BAM)? AND...suppose his personal account has a different password (and/or userid) as his BAM account? Where does BAM get the password for the projects he wants to join? Does BAM have authorization to pull this information from different projects so it can manage the new hosts that it needs to join up?

thanks!

-Doug

Because of this confusion with passwords/user ids (and not only for that ) BAM! requires that you sign up for BAM! with the same Username and password as in all project you participate in.

A general explanation of account Managers RPCs is located at http://boinc.berkeley.edu/acct_mgt.php

Thanks! That was what I was looking for.