| 2017-08-10 07:44:47 |
Kristin Chuang |
bug |
|
|
added bug |
| 2017-08-10 07:53:17 |
Kristin Chuang |
description |
===== steps =====
[1a] Complete console-conf process using foo@example.com
[1b] Check login status:
$ snap whoami
email: - #blank email info returned, should return foo's info
$ cat ~/.snap/auth.json
#~/.snap/auth.json exists, but no explicit foo related info listed in content
[2a] Do login with a new account bar@example.com
$ snap login bar@example.com
<enter password>
Login successful
[2b] Check login status:
$ snap whoami
email: foo@example.com #email info updated from blank to previous user foo, but should actually update to user bar
$ cat ~/.snap/auth.json
{"id":1,"username":"foo","email":"foo@example.com"...} #content updated to user foo's info, but should actually be updated to user bar's
[3a] Logout:
$ snap logout
[3b] Check login status:
$ cat ~/.snap/auth.json
cat: .snap/auth.json: No such file or directory
[4a] Try logging in again with bar@example.com
$ sudo snap login bar@example.com
<enter password>
Login successful
[4b] Check login status:
$ snap whoami
email: bar@example.com #correctly reflects current user
$ cat ~/.snap/auth.json
{"id":2,"email":"bar@example.com"...} #correctly updated with current user's info
===== expected result =====
`snap whoami` and ~/.snap/auth.json should correctly reflect the status of the current user
===== actual result =====
1. Note the difference between step 2a and 4a, 1b and 3b:
* ~/.snap/auth.json exists in 1b, while it does not in 3b.
* Step in 2a does not need sudo, while step in 4a does.
This indicates that, if I am not mistaken, foo is already logged in after console-conf completed, but not reflected correctly in `snap whoami` or ~/.snap/auth.json.
2. Note steps 2a & 2b:
User has been updated from foo to bar in these steps, but `snap whoami` and ~/.snap/auth.json is one step behind and just updates from blank user to previous user foo.
3. Note steps 3a and after:
The current user info is logged correctly only after a `snap logout` has been performed to reset the authentication details.
=> As a conclusion:
It seems like the initial user info is already incorrect, and will not update to the correct status unless a reset-like function `snap logout` is performed.
===== Core version =====
$ snap list
Name Version Rev Developer Notes
core 16-2.26.9 2381 canonical - |
===== steps =====
[1a] Complete console-conf process during system setup stage using foo@example.com
[1b] Check login status:
$ snap whoami
email: - #blank email info returned, should return foo's info
$ cat ~/.snap/auth.json
#~/.snap/auth.json exists, but no explicit foo related info listed in content
[2a] Do login with a new account bar@example.com
$ snap login bar@example.com
<enter password>
Login successful
[2b] Check login status:
$ snap whoami
email: foo@example.com #email info updated from blank to previous user foo, but should actually update to user bar
$ cat ~/.snap/auth.json
{"id":1,"username":"foo","email":"foo@example.com"...} #content updated to user foo's info, but should actually be updated to user bar's
[3a] Logout:
$ snap logout
[3b] Check login status:
$ cat ~/.snap/auth.json
cat: .snap/auth.json: No such file or directory
[4a] Try logging in again with bar@example.com
$ sudo snap login bar@example.com
<enter password>
Login successful
[4b] Check login status:
$ snap whoami
email: bar@example.com #correctly reflects current user
$ cat ~/.snap/auth.json
{"id":2,"email":"bar@example.com"...} #correctly updated with current user's info
===== expected result =====
`snap whoami` and ~/.snap/auth.json should correctly reflect the status of the current user
===== actual result =====
1. Note the difference between step 2a and 4a, 1b and 3b:
* ~/.snap/auth.json exists in 1b, while it does not in 3b.
* Step in 2a does not need sudo, while step in 4a does.
This indicates that, if I am not mistaken, foo is already logged in after console-conf completed, but not reflected correctly in `snap whoami` or ~/.snap/auth.json.
2. Note steps 2a & 2b:
User has been updated from foo to bar in these steps, but `snap whoami` and ~/.snap/auth.json is one step behind and just updates from blank user to previous user foo.
3. Note steps 3a and after:
The current user info is logged correctly only after a `snap logout` has been performed to reset the authentication details.
=> As a conclusion:
It seems like the initial user info is already incorrect, and will not update to the correct status unless a reset-like function `snap logout` is performed.
===== Core version =====
$ snap list
Name Version Rev Developer Notes
core 16-2.26.9 2381 canonical - |
|
| 2017-08-10 07:55:01 |
Tim Chen |
bug |
|
|
added subscriber Tim Chen |
| 2017-08-14 03:37:26 |
Kristin Chuang |
description |
===== steps =====
[1a] Complete console-conf process during system setup stage using foo@example.com
[1b] Check login status:
$ snap whoami
email: - #blank email info returned, should return foo's info
$ cat ~/.snap/auth.json
#~/.snap/auth.json exists, but no explicit foo related info listed in content
[2a] Do login with a new account bar@example.com
$ snap login bar@example.com
<enter password>
Login successful
[2b] Check login status:
$ snap whoami
email: foo@example.com #email info updated from blank to previous user foo, but should actually update to user bar
$ cat ~/.snap/auth.json
{"id":1,"username":"foo","email":"foo@example.com"...} #content updated to user foo's info, but should actually be updated to user bar's
[3a] Logout:
$ snap logout
[3b] Check login status:
$ cat ~/.snap/auth.json
cat: .snap/auth.json: No such file or directory
[4a] Try logging in again with bar@example.com
$ sudo snap login bar@example.com
<enter password>
Login successful
[4b] Check login status:
$ snap whoami
email: bar@example.com #correctly reflects current user
$ cat ~/.snap/auth.json
{"id":2,"email":"bar@example.com"...} #correctly updated with current user's info
===== expected result =====
`snap whoami` and ~/.snap/auth.json should correctly reflect the status of the current user
===== actual result =====
1. Note the difference between step 2a and 4a, 1b and 3b:
* ~/.snap/auth.json exists in 1b, while it does not in 3b.
* Step in 2a does not need sudo, while step in 4a does.
This indicates that, if I am not mistaken, foo is already logged in after console-conf completed, but not reflected correctly in `snap whoami` or ~/.snap/auth.json.
2. Note steps 2a & 2b:
User has been updated from foo to bar in these steps, but `snap whoami` and ~/.snap/auth.json is one step behind and just updates from blank user to previous user foo.
3. Note steps 3a and after:
The current user info is logged correctly only after a `snap logout` has been performed to reset the authentication details.
=> As a conclusion:
It seems like the initial user info is already incorrect, and will not update to the correct status unless a reset-like function `snap logout` is performed.
===== Core version =====
$ snap list
Name Version Rev Developer Notes
core 16-2.26.9 2381 canonical - |
===== steps =====
[1a] Complete console-conf process during system setup stage using email account foo@example.com
[1b] Check login status:
$ snap whoami
email: - #blank email info returned, should return foo's info
$ cat ~/.snap/auth.json
#~/.snap/auth.json exists, but no explicit foo related info listed in content
[2a] Do login with a new account bar@example.com
$ snap login bar@example.com
<enter password>
Login successful
[2b] Check login status:
$ snap whoami
email: foo@example.com #email info updated from blank to previous user foo, but should actually update to user bar
$ cat ~/.snap/auth.json
{"id":1,"username":"foo","email":"foo@example.com"...} #content updated to user foo's info, but should actually be updated to user bar's
[3a] Logout:
$ snap logout
[3b] Check login status:
$ cat ~/.snap/auth.json
cat: .snap/auth.json: No such file or directory
[4a] Try logging in again with bar@example.com
$ sudo snap login bar@example.com
<enter password>
Login successful
[4b] Check login status:
$ snap whoami
email: bar@example.com #correctly reflects current user
$ cat ~/.snap/auth.json
{"id":2,"email":"bar@example.com"...} #correctly updated with current user's info
===== expected result =====
`snap whoami` and ~/.snap/auth.json should correctly reflect the status of the current user
===== actual result =====
1. Note the difference between step 2a and 4a, 1b and 3b:
* ~/.snap/auth.json exists in 1b, while it does not in 3b.
* Step in 2a does not need sudo, while step in 4a does.
This indicates that, if I am not mistaken, foo is already logged in after console-conf completed, but not reflected correctly in `snap whoami` or ~/.snap/auth.json.
2. Note steps 2a & 2b:
User has been updated from foo to bar in these steps, but `snap whoami` and ~/.snap/auth.json is one step behind and just updates from blank user to previous user foo.
3. Note steps 3a and after:
The current user info is logged correctly only after a `snap logout` has been performed to reset the authentication details.
=> As a conclusion:
It seems like the initial user info is already incorrect, and will not update to the correct status unless a reset-like function `snap logout` is performed.
===== Core version =====
$ snap list
Name Version Rev Developer Notes
core 16-2.26.9 2381 canonical - |
|
| 2018-01-09 11:43:22 |
Maciej Borzecki |
snapd: assignee |
|
Maciej Borzecki (maciek-borzecki) |
|
| 2018-01-09 11:43:26 |
Maciej Borzecki |
snapd: status |
New |
Confirmed |
|
| 2018-01-09 15:08:40 |
Maciej Borzecki |
snapd: status |
Confirmed |
In Progress |
|
| 2018-01-10 14:04:09 |
Maciej Borzecki |
snapd: status |
In Progress |
Fix Committed |
|
| 2018-11-22 17:09:21 |
Paweł Stołowski |
snapd: status |
Fix Committed |
Fix Released |
|
