Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add KNOWN-ISSUES.md [CLI-118] #230

Merged
merged 1 commit into from
Apr 2, 2021
Merged

Add KNOWN-ISSUES.md [CLI-118] #230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions KNOWN-ISSUES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# Known Issues

1. [Storing the refresh token is not suported on WSL](#1-storing-the-refresh-token-is-not-suported-on-wsl)

## 1. Storing the refresh token is not suported on WSL

WSL users will get the following message upon successful login:
`Could not store the refresh token locally, please expect to login again once your access token expired.`

The Auth0 CLI uses the [go-keyring](https://github.com/zalando/go-keyring) library to securely store the refresh token across different operating systems. This is so every time the login credentials expire, the CLI can just silently renew them using the stored refresh token instead of having the user login again. However, that library [does not support WSL](https://github.com/zalando/go-keyring/issues/54), so the CLI will not store the refresh token on WSL. That means WSL users will have to log in again whenever the login credentials expire.