Skip to content

Feature Request: Allow marking coder_parameters as "sensitive" #9489

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
DolceTriade opened this issue Sep 1, 2023 · 3 comments
Closed

Feature Request: Allow marking coder_parameters as "sensitive" #9489

DolceTriade opened this issue Sep 1, 2023 · 3 comments

Comments

@DolceTriade
Copy link

Sometimes we might want to allow users to specify per-user credentials in the template so we can set up auth for them. It would be nice if we could mark these as sensitive so they don't autocomplete in the browser.
@cdr-bot cdr-bot bot added the feature label Sep 1, 2023
@matifali
Copy link
Member

matifali commented Sep 2, 2023

@DolceTriade Thanks for the feedback. Using a coder_parameter isn't recommended to store secrets. Can you talk more about your use cases and how you would like to use them to get user secrets? A sample template should work.
Also, I assume you will want to avoid the secret rendered in the UI.

To serve your purpose well, Coder may someday have user-level secrets.

@matifali matifali changed the title Feature Request: Allow marking coder_parameters as "sensitive" Feature Request: Allow marking coder_parameters as "sensitive" Sep 2, 2023
@DolceTriade
Copy link
Author

No, the user-level secrets is exactly our use case...To pre-authenticate users so that the environment is ready to go as soon as they start it. Otherwise, users have to create the environment and then manually authenticate with stuff... We can close this as a dupe of user level secrets.

@matifali
Copy link
Member

matifali commented Sep 2, 2023

Please feel free to leave your suggestions on the linked issue. It could help increase the priority of that feature. Currently, it is on roadmap-maybe

@matifali matifali closed this as not planned Won't fix, can't repro, duplicate, stale Sep 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DolceTriade @matifali