Activity log for bug #742678

Date Who What changed Old value New value Message
2011-03-25 18:23:52 Natalia Bidart bug added bug
2011-03-25 18:36:58 Natalia Bidart description Binary package hint: ubuntu-sso-client The Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, SSO REST API v1.0 allows passing a new parameter 'displayname' to the resgiter call, so we should un-hide the name text entry and send the user entered value to the SSO backend. Binary package hint: ubuntu-sso-client In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. On the other hand, the current proposed branch modifies an existent API as per: 158 - def register_user(self, email, password, captcha_id, captcha_solution): 159 + def register_user(self, email, password, displayname, 160 + captcha_id, captcha_solution): Is worth noting that the modified API is not meant to be used by any other app other than the GTK UI, but to complain with the freeze procedures I will be happy to propose a second branch where the register_user method maintains its original signature and add a new register_user_with_name method that will receive (and send) the new displayname parameter.
2011-03-25 18:50:33 Natalia Bidart ubuntu-sso-client (Ubuntu): milestone maverick-updates
2011-03-25 18:54:50 Natalia Bidart bug added subscriber Ubuntu Release Team
2011-03-25 18:55:44 Natalia Bidart bug added subscriber Roberto Alsina
2011-03-29 14:29:49 Joshua Hoover bug task added ubuntu-sso-client
2011-03-29 14:30:05 Joshua Hoover ubuntu-sso-client: assignee Naty Bidart (nataliabidart)
2011-03-29 14:31:11 Joshua Hoover ubuntu-sso-client: status New Triaged
2011-03-29 14:31:13 Joshua Hoover ubuntu-sso-client: importance Undecided Medium
2011-03-29 14:39:11 Joshua Hoover nominated for series ubuntu-sso-client/stable-1-0
2011-03-29 14:39:11 Joshua Hoover bug task added ubuntu-sso-client/stable-1-0
2011-03-29 14:41:28 Joshua Hoover ubuntu-sso-client/stable-1-0: status New Triaged
2011-03-29 14:41:41 Joshua Hoover ubuntu-sso-client/stable-1-0: importance Undecided Medium
2011-03-29 14:41:57 Joshua Hoover ubuntu-sso-client/stable-1-0: assignee Naty Bidart (nataliabidart)
2011-03-29 14:42:05 Joshua Hoover summary [FFE] Registration should require user full name [SRU] Registration should require user full name
2011-03-29 14:43:44 Joshua Hoover tags u1-maverick-sru
2011-03-29 19:33:15 Launchpad Janitor branch linked lp:~nataliabidart/ubuntu/natty/ubuntu-sso-client/ubuntu-sso-client-1.0.9
2011-03-29 19:38:14 Joshua Hoover description Binary package hint: ubuntu-sso-client In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. On the other hand, the current proposed branch modifies an existent API as per: 158 - def register_user(self, email, password, captcha_id, captcha_solution): 159 + def register_user(self, email, password, displayname, 160 + captcha_id, captcha_solution): Is worth noting that the modified API is not meant to be used by any other app other than the GTK UI, but to complain with the freeze procedures I will be happy to propose a second branch where the register_user method maintains its original signature and add a new register_user_with_name method that will receive (and send) the new displayname parameter. Binary package hint: ubuntu-sso-client In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. On the other hand, the current proposed branch modifies an existent API as per: 158 - def register_user(self, email, password, captcha_id, captcha_solution): 159 + def register_user(self, email, password, displayname, 160 + captcha_id, captcha_solution): Is worth noting that the modified API is not meant to be used by any other app other than the GTK UI, but to complain with the freeze procedures I will be happy to propose a second branch where the register_user method maintains its original signature and add a new --- TEST CASE: Need to NOT have a valid Ubuntu One token and the ability to create a new Ubuntu One account 1. Open System > Accessories > Passwords and Encryption Keys 2. Ubuntu SSO GUI should display with a name field at the top Expected result: Name field displays and is required (cannot be blank) register_user_with_name method that will receive (and send) the new displayname parameter.
2011-03-29 19:40:55 Joshua Hoover description Binary package hint: ubuntu-sso-client In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. On the other hand, the current proposed branch modifies an existent API as per: 158 - def register_user(self, email, password, captcha_id, captcha_solution): 159 + def register_user(self, email, password, displayname, 160 + captcha_id, captcha_solution): Is worth noting that the modified API is not meant to be used by any other app other than the GTK UI, but to complain with the freeze procedures I will be happy to propose a second branch where the register_user method maintains its original signature and add a new --- TEST CASE: Need to NOT have a valid Ubuntu One token and the ability to create a new Ubuntu One account 1. Open System > Accessories > Passwords and Encryption Keys 2. Ubuntu SSO GUI should display with a name field at the top Expected result: Name field displays and is required (cannot be blank) register_user_with_name method that will receive (and send) the new displayname parameter. Binary package hint: ubuntu-sso-client By not having the "displayname" field in the Ubuntu One registration screen, it results in confusing messages to be sent to users. An example is sharing a folder with a user where the user gets a message like: "New folder shared by <empty string>". This bug is fixed in Natty and has been tested. In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. On the other hand, the current proposed branch modifies an existent API as per: 158 - def register_user(self, email, password, captcha_id, captcha_solution): 159 + def register_user(self, email, password, displayname, 160 + captcha_id, captcha_solution): Is worth noting that the modified API is not meant to be used by any other app other than the GTK UI, but to complain with the freeze procedures I will be happy to propose a second branch where the register_user method maintains its original signature and add a new --- TEST CASE: Need to NOT have a valid Ubuntu One token and the ability to create a new Ubuntu One account 1. Open System > Accessories > Passwords and Encryption Keys 2. Ubuntu SSO GUI should display with a name field at the top Expected result: Name field displays and is required (cannot be blank) register_user_with_name method that will receive (and send) the new displayname parameter.
2011-03-29 19:41:12 Joshua Hoover bug added subscriber Ubuntu Stable Release Updates Team
2011-03-29 19:41:26 Joshua Hoover nominated for series Ubuntu Maverick
2011-03-29 19:41:26 Joshua Hoover bug task added ubuntu-sso-client (Ubuntu Maverick)
2011-03-29 19:41:38 Joshua Hoover ubuntu-sso-client (Ubuntu Maverick): milestone maverick-updates
2011-03-29 20:03:29 Natalia Bidart description Binary package hint: ubuntu-sso-client By not having the "displayname" field in the Ubuntu One registration screen, it results in confusing messages to be sent to users. An example is sharing a folder with a user where the user gets a message like: "New folder shared by <empty string>". This bug is fixed in Natty and has been tested. In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. On the other hand, the current proposed branch modifies an existent API as per: 158 - def register_user(self, email, password, captcha_id, captcha_solution): 159 + def register_user(self, email, password, displayname, 160 + captcha_id, captcha_solution): Is worth noting that the modified API is not meant to be used by any other app other than the GTK UI, but to complain with the freeze procedures I will be happy to propose a second branch where the register_user method maintains its original signature and add a new --- TEST CASE: Need to NOT have a valid Ubuntu One token and the ability to create a new Ubuntu One account 1. Open System > Accessories > Passwords and Encryption Keys 2. Ubuntu SSO GUI should display with a name field at the top Expected result: Name field displays and is required (cannot be blank) register_user_with_name method that will receive (and send) the new displayname parameter. Binary package hint: ubuntu-sso-client By not having the "displayname" field in the Ubuntu One registration screen, it results in confusing messages to be sent to users. An example is sharing a folder with a user where the user gets a message like: "New folder shared by <empty string>". This bug is fixed in Natty and has been tested. In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. --- TEST CASE: Need to NOT have a valid Ubuntu One token and the ability to create a new Ubuntu One account 1. Open System > Accessories > Passwords and Encryption Keys 2. Ubuntu SSO GUI should display with a name field at the top Expected result: Name field displays and is required (cannot be blank) register_user_with_name method that will receive (and send) the new displayname parameter.
2011-04-05 21:03:30 Martin Pitt ubuntu-sso-client (Ubuntu): milestone maverick-updates
2011-04-05 21:09:36 Natalia Bidart description Binary package hint: ubuntu-sso-client By not having the "displayname" field in the Ubuntu One registration screen, it results in confusing messages to be sent to users. An example is sharing a folder with a user where the user gets a message like: "New folder shared by <empty string>". This bug is fixed in Natty and has been tested. In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. --- TEST CASE: Need to NOT have a valid Ubuntu One token and the ability to create a new Ubuntu One account 1. Open System > Accessories > Passwords and Encryption Keys 2. Ubuntu SSO GUI should display with a name field at the top Expected result: Name field displays and is required (cannot be blank) register_user_with_name method that will receive (and send) the new displayname parameter. Binary package hint: ubuntu-sso-client By not having the "displayname" field in the Ubuntu One registration screen, it results in confusing messages to be sent to users. An example is sharing a folder with a user where the user gets a message like: "New folder shared by <empty string>". This bug is fixed in Natty and has been tested. In the GTK UI for SSO account creation, the Registration screen used to have a text entry for gathering the user full name. That field was hidden before maverick's final freeze because the SSO server side will not provide an API to actually set that value in the user account. Since last week, the SSO REST API v1.0 allows passing a new parameter 'displayname' to the "register" method (as per bug #709496), so we should un-hide the "name" text entry and send the value the user entered to the SSO backend. Currently, all the new SSO account are being created with an empty display name, causing (among other things) having the Ubuntu One shares be displayed as "New folder shared by <empty string>". Backporting this change will fix this issue. This change is not big at code level (see the branch proposed in bug #709494 for stable-1-0 series), since all the needed code and strings are already there (but hidden). Re-showing the "name" text entry will change how the UI looks (for the registration case, not for login), so this will require a UI freeze exception. As you can see in bug #709494, this is already fixed and released in natty. --- TEST CASE: Need to NOT have a valid Ubuntu One token and the ability to create a new Ubuntu One account 1. Open System > Accessories > Passwords and Encryption Keys 2. Ubuntu SSO GUI should display with a name field at the top Expected result: Name field displays and is required (cannot be blank) register_user_with_name method that will receive (and send) the new displayname parameter.
2011-04-05 21:15:02 Martin Pitt marked as duplicate 709494