Calling dotnet user-jwts while app is running causes malformed appsettings

[captainsafia]

No description provided.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[DamianEdwards]

I experienced a malformed appsettings.Development.json when using dotnet user-jwts yesterday and I definitely ran the tool while the file was open in Visual Studio, and very possibly while the app was running (but not sure). The resulting errors from dotnet user-jwts weren't great either, as the JWT manipulations operations would actually succeed, but I'd get an error in the console like:

'}' is invalid after a single JSON value. Expected end of data. Path: $ | LineNumber: 20 | BytePositionInLine: 1.

We should likely look at handling JSON exceptions in the tool and displaying a more user-friendly error message.

[glen-84]

This seems to be happening even if the app isn't running.

[mikeblakeuk]

I found just having my json formatted to 4 spaces instead of 2 kills it

1. dotnet user-jwts create
2. format based on EditorConfig to 4 spacess instead of 2
3. dotnet user-jwts create
4. view json

{
  "Authentication": {
    "Schemes": {
      "Bearer": {
        "ValidAudiences": [
          "https://localhost:44310"
        ],
        "ValidIssuer": "dotnet-user-jwts"
      }
    }
  }
}r": "dotnet-user-jwts"
            }
        }
    }
}

[ci-vamp]

not sure if its related but it keeps removing one of my valid audiences whenever i run the command to generate a token. please dont push this out to dotnet 8. its unusable in its current state

note: this happens whether:

• API is running or stopped
• appsettings has 2 or 4 space indents

notice it deletes the valid audience and then it mangles the file (you can see the red underline at the top) right after i create the token

2 space

removing-valid-audience.mov

4 space

in the case of 4 space it edits the file, sets it to 2 space then mangles

removing-valid-audience-4space.mov

[captainsafia]

OK -- I was able to get a repro and a bug fix for the original issue around malformed settings being written when the user-jwts CLI tool is being called twice.

@ci-vamp @mikeblakeuk I'm not sure if the presence of the editor config is a red herring in your scenarios. In any case, do you mind filling a separate issue for that so we can investigate it independently? I'll ping you when the bug fix for this one is merged in case it resolves your issues as well.