cloudfoundry / cloudfoundry/cli

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

Open
#1,933 25 comments 2 reactions 1 assignee View on GitHub

@a-b is already working on this.

Since Oct 1, 2024.

accepted
Dominant language
Go
Stars
1.9k
Forks
990
Avg merge
1d 7h
Merged PRs (30d)
8

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.