Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

cf login with certain options results in rename Access is denied error message

Aperta
#1,933 25 commenti 2 reazioni 1 assegnatario Vedi su GitHub

@a-b ci sta già lavorando.

Dal 1/10/2024.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

accepted

Please fill out the issue checklist below and provide ALL the requested information.

  • I reviewed open and closed github issues that may be related to my problem.
  • I tried updating to the latest version of the CF CLI to see if it fixed my problem.
  • I attempted to run the command with CF_TRACE=1 to help debug the issue.
  • I am reporting a bug that others will be able to reproduce.
    - [ ] If this is an issue for the v7 beta release, I've read through the official docs and the release notes.

Describe the bug and the command you saw an issue with
Trying to run cf login -a <api url> -o <org> -s Dev --sso but it does not work and instead returns Error writing config: rename C:\Users\<username>\.cf\temp-config696932450 C:\Users\<username>\.cf\config.json: Access is denied.

What happened
C:\Users\<username>\.cf\temp-config696932450 and C:\Users\<username>\.cf\config.json are left on file system. Inspecting config.json it looks incomplete. Manually moving temp-config696932450 to config.json appears to result in it working until next login.

Expected behavior
This command logs in without errors

To Reproduce

  1. Run cf login -a <api url> -o <org> -s Dev --sso
  2. Enter Temporary Authentication Code
  3. See error

Provide more context

  • Windows 10
  • cf login worked in this way through 6.46.1. Starting with 6.47.1 this no longer works.
  • note 6.47 refactored how cf login works which probably broke this - see https://github.com/cloudfoundry/cli/releases/tag/v6.47.0
  • Git bash, PowerShell, CMD... all same error
  • still broken in 6.51.0
  • API version: 3.66.0
  • I have confirmed with multiple users they have same issue
  • I have tried to catch what might be locking config.json using Process Explorer, Resource Monitor, etc. but none seem to catch anything locking config.json
Lingua principale
Go
Stelle
1.9k
Fork
990
Merge medio
1g 7h
PR unite (30g)
8

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudfoundry/cli

Tutte le issue di cloudfoundry/cli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.