Is it possible to create a second password for an account in BAM who’s only access would be to attach hosts to BAM!?

Basically what I can think of using this either in scripts, where if someone reads it, they can’t get the full access password (like the one we have now), or in a large corporation, we can tell our minions what username and P/W to use, but they can’t use the password to log into the BOINCStats website and make changes to my account.

willy? is this possible?

Everything is possible, it's a question of what do we want.

I'll think about this, I already have an idea but it has to cook a while first.

sounds good. I mostly wanted to get out the idea. I would think it may come in handly for some people.

Here's an idea. Don't check the password when a new host attaches. That way all you would need is the username to attach a client to the account manager. You would only need the password to log into the website and change settings.

Whichever way is done here, there will still be the problem that the authenticator for each project is in the account*.xml file.

I thought about the no-password option, but I have to check if there is information in the files that could be used to hack accounts.

Have you have any time to look into this further? My team is setting up an account where hosts would be joined by multiple people and it would be nice if we don’t have to worry about sending out passwords to them all. I see that other teams are doing similar things as well.

yes? no? thinkin about it?

Would be nice to have especially if you have Boinc on computers that belong to your older parents or friends and you do not want to share the password.

How about when connecting to BAM only enter the email address and username? No password that way.

btw, Willy which files are you talking about that could be hacked?