(2) the "username" in this case, is the full user e-mail. e.g., mitchellsundt@gmail.com The login dialog is provided by the web browser and
the prompt label ("Username") is not configurable, so this will be an
ongoing training issue if your users use this mechanism for logging onto the
website. This is because we are using the built-in Digest or Basic
authentication protocol.
(3) if you are logged onto the Aggregate sever using a gmail account, you
can change your own password by choosing the "Change User Password" link
under the "Manage" heading on the right side of the links displayed at the
top of the Aggregate homepage.
(4) if you are the superuser or administrator for the website, you can
choose the "Configure Site Access" link under the "Manage" heading. There
will be a link within the "Site Access" / "User Password" section that
enables you to set the passwords for any or all users that you have defined
for the system (you define them by supplying their e-mail addresses in the
data entry boxes on that screen).
(5) if you are capable, you may want to build 1.0 from the source tree, as
there were a few subtle changes to allow ODK Collect 1.1.6 to use https and
authentication when communicating to the server. Those changes are in the
development tips of ODK Collect 1.1.6 and Aggregate v1_0.
···
------------
Mitch
On Mon, Apr 18, 2011 at 12:48 AM, Arjun Chandra Das arjun@icddrb.orgwrote:
Hi:
I’ve configured local instance of ODKAggregate v1.0 alpha 6 under
apache-tomcat-6.0.29 on my PC.
On a separate note, is it possible to have users change their Aggregate password? I have a bunch of users who want to be able to change their own Aggregate passwords (not Google Account), and am struggling to figure out how this would work.
Perhaps on the alpha 6 (too loong ago to recall what that had), but not on
the current code. We eliminated that feature since the primary use of the
Aggregate password was for ODK Collect device connections, and most
deployments use one Aggregate username/password for their fleet of devices
-- it would be too risky if one user accessed the site and decided to
change the password.
On a separate note, is it possible to have users change their Aggregate
password? I have a bunch of users who want to be able to change their own
Aggregate passwords (not Google Account), and am struggling to figure out
how this would work.