[JIRA] (JENKINS-59482) Improve UX for selecting user-scoped credentials
Title: Message Title
Vít Zikmund edited a comment on JENKINS-59482
Re: Improve UX for selecting user-scoped credentials
Thanks for your consideration {color:#1d1c1d}FYI:{color}{color:#1d1c1d} [~jvz] , as author of the latest change you might want to put in your 2¢.{color}{color:#1d1c1d} [~stephenconnolly] (I know you’re very busy) since you have a vision for how user credentials work you may be interested too . {color}{color:#1d1c1d}Apologies for not explaining why I was tagging you originally in this comment.{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202097.1569241421000.3246.1569246060130%40Atlassian.JIRA.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Vít Zikmund edited a comment on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline Hello there, [~jvz]. If you suggest using the authorize- project plugin for this purpose, can you confirm it actually works? All my white-box attempts so far failed as those in JENKINS-44772. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175380.1476360951000.3092.1569243121730%40Atlassian.JIRA.
[JIRA] (JENKINS-38963) User-scoped credentials cannot be looked up in pipeline
Title: Message Title Vít Zikmund commented on JENKINS-38963 Re: User-scoped credentials cannot be looked up in pipeline Hello there, Matt Sicker. If you suggest using the authorize-plugin for this purpose, can you confirm it actually works? All my white-box attempts so far failed as those in JENKINS-44772. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175380.1476360951000.3090.1569243121708%40Atlassian.JIRA.
[JIRA] (JENKINS-59482) Improve UX for selecting user-scoped credentials
Title: Message Title Vít Zikmund commented on JENKINS-59482 Re: Improve UX for selecting user-scoped credentials Thanks for your consideration Matt Sicker Stephen Connolly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202097.1569241421000.3060.1569242640165%40Atlassian.JIRA.
[JIRA] (JENKINS-59482) Improve UX for selecting user-scoped credentials
Title: Message Title Vít Zikmund created an issue Jenkins / JENKINS-59482 Improve UX for selecting user-scoped credentials Issue Type: Improvement Assignee: Unassigned Components: credentials-plugin Created: 2019-09-23 12:23 Environment: credentials-2.3.0 Priority: Minor Reporter: Vít Zikmund Hi there, since JENKINS-58170 there's a new checkbox - "List user credentials" in the credentials parameter, that's by default unchecked. When checked, the user-scoped secrets can be selected from the drop-down. This changed the previous behavior which had no checkbox and the drop-down contained the user-scoped creds by default. Although I think I understand the reasoning behind why it was added, I don't think all users need to explicitly consent twice that they want to select a user-scoped credential. My whole team uses these parameters as a workaround to JENKINS-44772 several times a day and we all would be thrilled for a fix. As I know there's quite some hesitance to fix it at all, we'll be grateful for at least some old-days compatible UX: One approach could be to add a config option for the default state of the user-scoped checkbox in the configuration/pipeline script (along these lines). Another option could be to allow selecting user-scoped credentials by default as before, but display the warning when a user-scoped credential gets selected. Both options are IMHO quite easy to implement and they would give users more control while retaining the new safety measures where desired.
