{"action":"closed","issue":{"url":"https://api.github.com/repos/aspnet/DotNetTools/issues/405","repository_url":"https://api.github.com/repos/aspnet/DotNetTools","labels_url":"https://api.github.com/repos/aspnet/DotNetTools/issues/405/labels{/name}","comments_url":"https://api.github.com/repos/aspnet/DotNetTools/issues/405/comments","events_url":"https://api.github.com/repos/aspnet/DotNetTools/issues/405/events","html_url":"https://github.com/aspnet/DotNetTools/issues/405","id":303981464,"node_id":"MDU6SXNzdWUzMDM5ODE0NjQ=","number":405,"title":"Flattened user-secrets not compatible with Visual Studio for Windows Secrets Manager.","user":{"login":"rcollette","id":136476,"node_id":"MDQ6VXNlcjEzNjQ3Ng==","avatar_url":"https://avatars0.githubusercontent.com/u/136476?v=4","gravatar_id":"","url":"https://api.github.com/users/rcollette","html_url":"https://github.com/rcollette","followers_url":"https://api.github.com/users/rcollette/followers","following_url":"https://api.github.com/users/rcollette/following{/other_user}","gists_url":"https://api.github.com/users/rcollette/gists{/gist_id}","starred_url":"https://api.github.com/users/rcollette/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rcollette/subscriptions","organizations_url":"https://api.github.com/users/rcollette/orgs","repos_url":"https://api.github.com/users/rcollette/repos","events_url":"https://api.github.com/users/rcollette/events{/privacy}","received_events_url":"https://api.github.com/users/rcollette/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-03-09T21:11:26Z","updated_at":"2018-11-20T01:39:44Z","closed_at":"2018-11-20T01:39:44Z","author_association":"NONE","body":"If secrets with nested keys are created in Visual Studio for Windows secrets manager, the following code works just fine.\r\n```\r\n            var signingKeys = Configuration.GetSection(\"Tokens:AuthToken:SigningKeys\");\r\n            foreach (var key in signingKeys.GetChildren())\r\n            {\r\n                issuerSigningKeys.Add(new SymmetricSecurityKey(Encoding.UTF8.GetBytes(key.Value)));\r\n            }\r\n```\r\nHowever, a design decision was made to not support nested secrets in the cli tool.  I wind up having \r\nto hand create the secrets.json file, and its containing folder.\r\n\r\n```\r\n{\r\n    \"Tokens\": {\r\n        \"AuthToken\": {\r\n            \"SigningKeys\": {\r\n                \"SigningKey1\": \"\",\r\n                \"SigningKey2\": \"\"\r\n            }\r\n        }\r\n    }\r\n}\r\n```\r\nHow is it that there is some disconnect between what Visual Studio Windows does and what the CLI does.  I'm on a mac so I have to use the CLI tool\r\n\r\nI know there was also discussion about discouraging hand editing the file, but that is exactly what I am having to do because of this disconnect."}}
{"actor":{"display_login":"natemcmaster"}}