I have a TrueNAS server with two afp shares and an smb share on it. In the keychain of my mac system I can see the saved credentials for one of the afp shares, and for the smb share. But I can't see any saved credentials for the second afp share.

However from Finder when I do a "Go => Connect to Server" and enter the details of the second afp share, my mac connects to this share without asking me for that share's credentials. But this share does have credentials on the server side so I believe that the credentials for it are being cached somewhere on my mac.

So if the credentials are not being cached in my keychain, where else could they be cached?

The reason I ask is that I believe that the cached credentials for this second afp share are wrong and I want to try and reset them.


I just changed the password on the server side and now I cannot connect to that second afp share. OS X reports "There was a problem connecting to the server", but doesn't prompt me for any new credentials. This says to me that the credentials are being cached somewhere.

1 Answer 1


Things are way weirder than I thought! The way that I access my three shares is:

  1. afp://
  2. afp://
  3. smb://

With all the entries deleted from the keychain and I do a "Connect to server", I am prompted for the server side credentials. If I enter them and do not check "Remember this password in my keychain", then all is well and I can correctly log into any of the shares.

The issue seems to be when I do check "Remember this password in my keychain". From experimenting, the keychain only remembers the credentials per IP address and per protocol. So that there was always only ever 2 different entries in my keychain: one for afp:// and one for smb:// and that the keychain would ignore the share name itself for a single protocol/IP pair when retrieving the server credentials.

So the sequence of events seems to be:

  1. (no credentials in keychain)
  2. Access afp Share1
  3. Prompted for credentials for Share1
  4. Check "Remember.." and the correct credentials are saved for share1 in my keychain.
  5. Access afp Share2
  6. The keychain gets excited and says "Hey I've got credentials for that IP address and that protocol - here they are!!!!!" and totally ignores the share name itself.
  7. Somehow the system then connects to afp Share2, but with the wrong password.
  8. With the wrong credentials applied, I end up with a read only access to the share.

I only noticed this because previously I hadn't saved the password for either of the afp shares. Over the weekend I updated the server and as a part of checking that I could access the shares I finally checked the "remember .. " check box. But I didn't get an error or notice that the second share was read only until today when I was trying to use the system.

I did check the smb share and this was connecting as read/write.

Note that I tried to fix things in my Keychain by renaming the afp share entry in order to disambiguate the two afp shares. However this didn't solve anything. It seems the keychain only cares about protocol/IP pairs

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .