Seahorse can't unlock ssh key

I installed Leap 42.1 over the weekend and I set up my domain (samba) account, and logged in. I copied my ssh key from my archive and the first time I tried to use it seahorse asked for my password, which I can see is now saved in Seahorse, but every time I use the ssh key, the shell asks me for the password still.

Looking at the journalctl logs I can see the following:

Nov 30 10:26:45 stockpot.DOMAIN.COM su[28849]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/10000/keyring/control
Nov 30 10:26:45 stockpot.DOMAIN.COM su[28849]: gkr-pam: couldn't unlock the login keyring.
Nov 30 10:26:45 stockpot.DOMAIN.COM su[28849]: pam_unix(su-l:auth): authentication failure; logname=SMB01\username uid=10000 euid=0 tty=pts/1 ruser=SMB01\username rhost=  user=root
Nov 30 10:26:45 stockpot.DOMAIN.COM su[28849]: pam_winbind(su-l:auth): getting password (0x00000390)
Nov 30 10:26:45 stockpot.DOMAIN.COM su[28849]: pam_winbind(su-l:auth): pam_get_item returned a password
Nov 30 10:26:45 stockpot.DOMAIN.COM su[28849]: pam_winbind(su-l:auth): request wbcLogonUser failed: WBC_ERR_AUTH_ERROR, PAM error: PAM_USER_UNKNOWN (10), NTSTATUS: NT_STATUS_NO_SUCH_USER, Error message was: No such user

uid 10000 is my domain user account, I’m not sure why it is saying it is not owned by me.

Can anyone suggest a way to get this key to unlock with my gnome login?

I later noticed that my auth wasn’t forwarding to remote hosts, and in finding a fix for that, I found this page:

http://serverfault.com/questions/404447/why-is-ssh-agent-forwarding-not-working

This also appears to have fixed my issue with Seahorse remembering my key:

ssh-add -k