Github: GitHub Plugin does not remember token

[KINFOO]

Prerequisites

• Reproduced in Safe Mode
• FAQs on the message board checked
• Bug isn't already filed
• Debugging guide followed

Description

_GitHub_ plugin asks for a token at every startup.

Steps to Reproduce

1. Open _Atom_
2. Open a file from a _GitHub repository_
3. Toogle _GitHub pannel_

   

4. Click _Login_

   

5. Provide _token_
6. Login is successful
7. PR content is available
8. Restart _Atom_
9. _GitHub pannel_ asks for token, __again__

   

Expected behavior:

_GitHub_ plugin remembers token.

Reproduces how often:

100%

Versions

You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.

$ atom --version
Atom    : 1.18.0
Electron: 1.3.15
Chrome  : 52.0.2743.82
Node    : 6.5.0
$ uname -a
Linux hendrix 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2 (2017-06-12) x86_64 GNU/Linux

[hamza]

A similar issue is happening with me too. Put it up on the forum

[hamza]

Try this as a solution https://github.com/atom/github/issues/457

Worked for me to use

brew install git

It appears the macOS native git doesn't play well with this package

[BinaryMuse]

@KINFOO On Linux, we rely on libsecret to remember this token (via keytar). Do you have a keyring manager installed?

Also, if you look in the developer tools, do you see a warning saying "Using an InMemoryStrategy strategy for storing tokens"?

[BinaryMuse]

@hamzatayeb Your issue is not the same; it looks like it might be a duplicate of https://github.com/atom/github/issues/861

[KINFOO]

@hamzatayeb I am running Linux,
I think brew won't help.
But thanks

[KINFOO]

$ apt search libsecret
...
libsecret-1-0/stable,now 0.18.5-3.1 amd64  [installé, automatique]
  stockage secret

@BinaryMuse libsecret is installed.
In the console, I read:

Using an InMemoryStrategy strategy for storing tokens. The tokens will only be stored for the current window

I am using _KDE Plasma_, I think my _keyring manager_ has issues.
It asks me for Git password at computer startup.
Looks like configuring ksshaskpass is a pain, a KDE Wallet pain.

Thanks for the valuable help

[hamza]

@KINFOO ah yeah sorry about that. Good luck

[KINFOO]

@BinaryMuse I fixed the ksshaskpass issue.

Now, when I start my computer, I am no longer asked for password.
I can navigate to some _private_ repository and perform a fetch without providing password.

Still when I provide _Atom_ a token, it still does not remember it.
Console still displays:

Using an InMemoryStrategy strategy for storing tokens. The tokens will only be stored for the current window

Hope it helps

[jvican]

I'm having the same problem in Linux, but the console doesn't display anything. I have gnome-keyring installed, so I don't see why it doesn't work.

Could someone give me some pointers to further debug what's going on?

[maxsupermanhd]

Still an issue? Guys are you working on this thing or its completely dead? Why I am supposed to regenerate token for a text editor every time i want to work with remotes?

[ajjr1996]

Same issue here

[l4tte]

Hey guys! You have to install gnome-keyring because the default one on my system (Arch) is broken with atom. In order to install gnome-keyring on a non-gnome WM, use the PAM method

[EmmanuelLM]

Same issue here but using Atom under ChromeOs (via Linux emulation).
Would be good to not make the solution dependent on a GUI component (appreciate this is probably a minority of use cases)