macOS Sierra always prompts for credentials for network drives

Somewhere in the original post for this topic, someone mentioned an app (available in the Mac App Store) called Automounter. I just bought it ($9.99 plus tax) and can report that it does work as claimed, and restores network-volume automount capability to Mac Sierra. SMB, NFS and AFP shares are supported, as are NAS devices. Once configured, it runs at login to mount the volumes to the Mac desktop, no Connect-button clicking needed. Then during normal operation it sits unobtrusively in the menu bar, ready for further configuration.

I'm not at all complaining or begruding the app developer the money charged for his software, but it is somewhat ironic that, while the Mac Sierra OS itself is free, it costs users $10 to restore a functionality lost in the upgrade from earlier systems. Seems to me the more sensible approach would have been a Security System Preference control allowing users the choice of always prompting for credentials or not. Maybe someday there will be...

here is a thread where they discuss a work-around by using apple script and adding it to login items:

https://forums.developer.apple.com/thread/51045

if i were on Sierra i would try it out. but i'm not upgrading just to try it.

that solution is not straightforward for many mac users, and would be something which apple would need to make the computer do for the user when a user wants to map/connect to a nas or share.

I don't think Apple intends this behavior. in fact, Apple's own support page contradicts that assertion:

macOS Sierra: Connect to shared computers and file servers on a network

I'm not talking about auto mounting a share but this issue exists when trying to connect manually to a network drive as well. I suspect the bug is security related in some way, but it's beyond me. Maybe 10.12.2 will address the issue.

Fixed!

Definitely not a bug, as per the item below. But, for crying out loud(!), their thinking is inconsistent because you can still mount your shares from a Finder window and NOT have to enter credentials. Whatever. The following works.

https://support.apple.com/en-us/HT207112

This appears elsewhere in the thread, but just to reinforce, if 10.12.2 alone doesn't fix this problem for you (as, oddly, it seems to have for some), then in addition you (may!) need the advice here:

If you're asked to click Connect before reconnecting to a server - Apple Support

That seems to have fixed the prompting-at-login for me..

However, I don't know if it'll fix the occasionally dropped connections, failure to reconnect, or (program-crippling) "-1" naming of /Volumes/ mounts when they remount, or strange change-of-mountpoint-ownership when using auto_fs mounts....

-So I think I may pay my $6.99 and try http://www.pixeleyes.co.nz/automounter/index.html :-(

Same here.

My NAS auto mounts normally now.

No need to do anything special. But we might want to save this in a handy place for a rainy day: If you're asked to click Connect before reconnecting to a server - Apple Support

Cheers!

Unfortunately, macOS Sierra - SMB is the default and logins require sign in every time regardless if it's saved in Keychain.

I'm not sure about AFP logins. You might try AFP only and turn off SMB to see if that works for you. Although, for your NAS, it may require SMB.

Hi,

I have this problem too. I have a qnap Nas and 3 macs, 2 with sierra and 1 with el capitan. On El Capitan it's all ok i do an Automator Application and add to login in.

On sierra, system always pops up the authentication dialogue. This is not good especially for one who use macmini like a mediaserver (itunes library and audirvana) without keyboard mouse and monitor connected.

This is absolutely crazy and completely nonsensical. If you click the auto-discovered NAS share (in my case QNAP) in Finder without having entered credentials (again) you get the error 'NASNAME' can't be opened because the original item can't be found.

Who could have possibly thought this was a good idea? I hope to God(c) this is a bug!!

I'm not at all complaining

you really should be, imo. it's core functionality that was removed (supposedly by intent). so in this situation you had to spend $ 10 to obtain an app that will restore that function. do you see where this is going ?

when i had bought my app, called Drive Mounter - more than a year ago - it was because i put my shares into login items. they auto-mounted fine, but i would always be presented with the finder window of that share after OS 10 mounted the shares. this is despite using the Hide toggle for them. When using Drive mounter for the shares, the Finder windows never appear when I log in and the shares mount. Whether this app is conflicting with or causing some subroutine errors in OS 10, I do not know. I know it takes a minute for both shares to mount on the desktop after a restart of the OS.

so what I really did was buy an app in order to compensate for a lack in functionality of the OS or an issue that was never addressed even though Apple is aware of that.

today we have these 2 issues together - and Apple is aware of that. or are they really ?

the goal of this thread is to get the issues fixed. hence, everyone's question is: WHEN ?

Thanks this app works well, in my country cost 14,98 €....it's very expensive in my opinion for what it does but for now it's the only solution...😐😐😐 if you think that El Capitan do it for free with an Automator Simple workflow....

I Hope Apple solves the problem.

Stay Connected....

in the app store, security update 2016-002 just made itself available. i was reading thru the list of security "holes" it plugs. one in particular got my attention:

OpenSSH

Available for: OS X Mavericks v10.9.5, OS X Yosemite v10.10.5, and OS X El Capitan v10.11 to v10.11.3

Impact: Connecting to a server may leak sensitive user information, such as a client's private keys

Description: Roaming, which was on by default in the OpenSSH client, exposed an information leak and a buffer overflow. These issues were addressed by disabling roaming in the client.

does this impact connections with NAS drives ?

reminder: i am on OS X 10.11.6, not 10.12.

i decided to apply 2016-002 and so far the persistent authentication for connecting to my shares has not appeared - i am still using 10.11.6.

PleasantSpectrum,

i can see how apple would want to try to prohibit someone or a program which is not authorized from connecting to a network share, and that itself would be a great functionality of an OS.

sierra implementation is not working for us, we are connecting to a server with root privileges in the OS, which i think should be good enough to not have to worry much about unauthorized access to a home network NAS or other device.

has anyone ever encountered a situation like that where unauthorized access to their NAS happened from a mac or windows box within their network ?

I too only connect to my NAS, and after switching to Sierra, the automatic - without re-prompt for credentials was, and still is "Broke". But I did find one thing that fixed mine, and it was a program I read on another post here, called AutoMounter,...shouldn't have to use a third-party app for something that was working fine, but at least I'm connecting without that annoying re-prompt now.

We have this problem across our whole office too! We are very much regretting updating to Sierra. 😠

It can't be a "feature" as Apple claims because the logic is very flawed.

It totally contradicts the point of the keychain and saving credentials. If this new feature was intended to improve security then the user should be required to actually enter the credentials at the prompt, and saving should not be an option. However the since the credentials are saved in the keychain, this subsequent user interaction is absolutely unnecessary and makes no sense. It's only a nuisance to require user interaction for authentication where the credentials are already saved in the keychain.

Hence imho this is a BUG!