From b92bd2d53e5de6ac40cb97fca104bacef2dbf4c0 Mon Sep 17 00:00:00 2001 From: Rita Zerrizuela Date: Fri, 2 Apr 2021 18:26:40 -0300 Subject: [PATCH] Add KNOWN-ISSUES.md (#230) --- KNOWN-ISSUES.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 KNOWN-ISSUES.md diff --git a/KNOWN-ISSUES.md b/KNOWN-ISSUES.md new file mode 100644 index 000000000..9ada4c30b --- /dev/null +++ b/KNOWN-ISSUES.md @@ -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.