[JIRA] (JENKINS-56298) 'authenticated' role not shown in role strategy using AD
Title: Message Title Bob Ashforth updated JENKINS-56298 I actually found that although the role 'authenticated' does not appear, once I had my AD settings working completely and correctly, when I "created" the role it was recognized as a 'user' for which I could define permissions. Closing the bug accordingly. Jenkins / JENKINS-56298 'authenticated' role not shown in role strategy using AD Change By: Bob Ashforth Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56298) 'authenticated' role not shown in role strategy using AD
Title: Message Title Bob Ashforth created an issue Jenkins / JENKINS-56298 'authenticated' role not shown in role strategy using AD Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin, role-strategy-plugin Created: 2019-02-26 20:25 Environment: Administration of Jenkins 2.138.1 Priority: Major Reporter: Bob Ashforth I'm using Jenkins 2.138.1, with the Active Directory plugin used for authorization. This is working, as indicated by the population of group membership for users who have logged into the system. I've also selected the role-based strategy, which is supposed to include a built-in 'authenticated' role which is assigned to any and all logged-in users. This role does not show up, and if I create it and assign specific permissions to the role, those permissions are not applied to logged-in users. Another Jenkins instanced used by my team is using the Matrix-based project security, and that plugin provides both Anonymous Users and Authenticated Users built-in 'roles.' I'd really like to continue with the role-based approach, in order to make use of folder and node ownership for corresponding teams. I hope this issue can be prioritized for triage, at least.
[JIRA] (JENKINS-54897) Unexpected error in launching a agent after restart
Title: Message Title Bob Ashforth commented on JENKINS-54897 Re: Unexpected error in launching a agent after restart Can you recommend any workarounds? This is crippling a major lift-and-shift project for us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
