After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732940 - Nautilus doesn't unlock GOA credentials
Nautilus doesn't unlock GOA credentials
Status: RESOLVED DUPLICATE of bug 693578
Product: nautilus
Classification: Core
Component: general
3.12.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-07-09 08:52 UTC by romu
Modified: 2015-05-18 18:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description romu 2014-07-09 08:52:08 UTC
Hi,
Some weeks ago, I tried to file a bug on GOA because, as a user, I'm not warned when my Windows credentials get outdated. I've been answered this is not a GOA issue, but it's applications related.

So here I am, filling this issue. The sequence is the following:

Pre-condition: your Windows credentials are outdated

1. Browse your LAN
2. Try to connect a Windows share
3. Nautilus asks for credentials
-> Enter the needed information
4. You're connected to the requested share

-> BUT, if you go to the GOA applet, you'll see your Windows credentials are still outdated, Nautilus didn't refresh them.

The way all of this currently works is really annoying when we use Gnome in the Windows world. There is no warning your credentials are outdated, and if Nautilus doesn't unlock them, everytime you'll need to access a Windows share, you'll be asked for credentials.
Comment 1 Cosimo Cecchi 2014-09-13 06:07:53 UTC
I don't understand this; what is the GOA applet? I don't think GOA supports SMB credentials at the moment.

Debarshi, is there something I'm missing?
Comment 2 Debarshi Ray 2014-09-13 09:46:08 UTC
(In reply to comment #0)

> Some weeks ago, I tried to file a bug on GOA because, as a user, I'm not
> warned when my Windows credentials get outdated. I've been answered this
> is not a GOA issue, but it's applications related.

That is right. Earlier when your credentials expired we used to through a desktop-wide notification. We removed that because it would pop-up even when there was no visible application. Instead we mandate that if an application fails to use an online account due to expired credentials it should handle it in its own UI by showing an in-app notification.

But ...

> So here I am, filling this issue. The sequence is the following:
> 
> Pre-condition: your Windows credentials are outdated
> 
> 1. Browse your LAN
> 2. Try to connect a Windows share
> 3. Nautilus asks for credentials
> -> Enter the needed information
> 4. You're connected to the requested share

GOA does not support Samba in any form. The Windows Live account that you see is about Microsoft's cloud services - OneDrive (earlier known as SkyDrive), Outlook.com, etc., but not SMB or Windows share.
Comment 3 romu 2014-09-14 15:00:03 UTC
My mistake, it's a kerberos account ("Enterprise Login" in GOA) to connect my Active Directory, so my SMB shares.

Can I edit the PR description to correct?
Comment 4 António Fernandes 2015-05-16 11:57:00 UTC
romu: What happens if you update the "Enterprise Login" credentials in the "Online Accounts" Settings panel? Will nautilus no longer ask for credentials when connecting to a Share?
Comment 5 romu 2015-05-16 12:53:55 UTC
Yes Antonio, that's it. I've taken the habit to unlock the credentials (on the GOA settings panel) manually each morning when connecting my PC.
Comment 6 António Fernandes 2015-05-16 14:14:28 UTC
I see. Indeed, it's not a good user experience if the user must remember to authenticate before trying to access network resources.

[I think the developers questions have been answered. Changing status to NEW.]
Comment 7 Debarshi Ray 2015-05-18 17:27:33 UTC

*** This bug has been marked as a duplicate of bug 693578 ***
Comment 8 romu 2015-05-18 18:11:51 UTC
You probably know this better than me but I don't see where it is similar of the bug 693578.

Because I always start my PC connected to my company network and I never get the Kerberos token automatically. So, I always have to get GOA and then refresh the token manually.

But if you're sure this is the same issue, that's fine to me. Thanks.