Client credentials auth failing when no keyring about auth0-cli HOT 6 CLOSED

On Wed, Dec 6, 2023 at 9:11 AM Michael Christenson II < ***@***.***> wrote: @mgrand-kubra <https://github.com/mgrand-kubra> I found one way to duplicate the second error, but it required me to remove the access_token key from a tenant in ~/.config/auth0/config.js. When I logged back in, it healed itself. Is there any chance that the file got corrupted or hand-edited? I did try multiple ways of failing, including removing the write permission from the config file. None of the other forms gave that error message. Do you mind trying to remove ~/.config/auth0/config.json and re-signing in? If that doesn't work, at least we've eliminated one known possibility. — Reply to this email directly, view it on GitHub <#933 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7M6DICLPKD3JY4RPPMYX3LYIB4KJAVCNFSM6AAAAABAF74HLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBSHE3DMMRWGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

On Tue, Dec 5, 2023 at 2:59 PM Michael Christenson II < ***@***.***> wrote: @mgrand-kubra <https://github.com/mgrand-kubra> I'm looking into this and I want to make sure my setup is close to yours. What version of WSL2 does uname -a give you? Mine is 5.15.133.1-microsoft-standard-WSL2 — Reply to this email directly, view it on GitHub <#933 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7M6DIFXUQAEL6UOA7IK6SDYH54KTAVCNFSM6AAAAABAF74HLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBRGUZDOMRSGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

***@***.***:~/tmp$ auth0 --version auth0 version 1.3.0 2bd069c ***@***.***:~/tmp$ auth0 login --domain $AUTH0_DOMAIN --client-id $AUTH0_CLIENT_ID --client-secret $AUTH0_CLIENT_SECRET ▸ Could not store the client secret and the access token to the keyring: The name org.freedesktop.secrets was not provided by any .service files ▸ Expect to login again when your access token expires. ▸ Successfully logged in. ▸ Tenant: terraform-sandbox2.kubra-idp-dev.auth0.com ▸ Hint: Switch between authenticated tenants with `auth0 tenants use <tenant>` ***@***.***:~/tmp$ auth0 tf generate --output-dir tmp === dev.kubra-idp-dev.auth0.com error ▸ failed to fetch access token using client credentials: failed to retrieve client secret from keyring: The name org.freedesktop.secrets was not provided by any .service files This may occur if the designated Auth0 application has been deleted, the client secret has been rotated or previous failure to store client secret in the keyring. Please re-authenticate by running: auth0 login --domain <tenant-domain --client-id <client-id> --client-secret <client-secret> ***@***.***:~/tmp$ On Mon, Dec 4, 2023 at 8:57 AM Will Vedder ***@***.***> wrote: I believe that this was resolved with #919 <#919> and released with 1.3.0 <https://github.com/auth0/auth0-cli/releases/tag/v1.3.0>. Are you able to upgrade and retry? — Reply to this email directly, view it on GitHub <#933 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7M6DIE6BXM5H7345YLKJSLYHXJFNAVCNFSM6AAAAABAF74HLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZYGY4TIOJXGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>