Actually, with the local jenkins user database, my CLI connection doesn't really work. It succeeds to start a build, but my build won't work because my node goes away. It only seems to have the built in internal node. So the only way my jenkins install is now functional is with security completely turned off. Is there ANYONE able to help me with this?
On Monday, September 15, 2025 at 11:36:50 AM UTC-6 [email protected] wrote: > I tried using Mixing Security Realm. I saw an issue in the plugin where > AD stopped working in it quite some time ago that never appears to have > been addressed so I wasn't confident going in. I installed it, set the > security realm to mixing. I noticed that none of the options for realms > under mixing was "Jenkins own user database" but tried to turn on AD > thinking maybe that one came by default. The AD integration didn't work. > I was able to test the AD connection (succeeded), but once I saved down the > changes, it errored restarting jenkins. After that I tried a logon but > neither my AD user nor a local user succeeded. Disabled security and went > back to local jenkins user database. That seems to be the only way I can > continue to have my CLI integration work. Is there someplace I can open a > ticket on this? Thanks! > > On Saturday, September 13, 2025 at 3:52:11 AM UTC-6 [email protected] > wrote: > >> I turned off AD, enabled the local jenkins users database, and created a >> local user with ssh key. I can ssh remotely with that user and interact >> with jenkins. I can also login with that user directly. In Jenkins >> 2.516.1, there is no longer the option to fallback to local user if AD >> fails. I don't believe this is working because as soon as I enable AD >> again, the local user fails on all fronts. I know it used to work because >> that's how I had it set up prior to 2.516.1. Does anyone have an >> information on this? Thanks! >> >> On Monday, September 8, 2025 at 8:42:17 AM UTC-6 [email protected] >> wrote: >> >>> Anyone have any clue on this? Thanks! >>> >>> On Fri, Sep 5, 2025 at 7:44 AM [email protected] <[email protected]> >>> wrote: >>> >>>> Yesterday I had to update AD since we moved to 2.516.1. Not sure how I >>>> had it set up before but I can no longer ssh from an automated job to >>>> start >>>> a build. It's giving permission denied. Looking at the documentation for >>>> the CLI, it looks like I had a user set up with their public key under >>>> Security/Users. Well since I have AD selected for security realm, I don't >>>> have the option to set up my users. How do I do both like I did before? >>>> Thanks! >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Users" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-users/BGiM4-7v0NI/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/74a21acd-c768-4317-acf5-68fb4a6bcad4n%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/74a21acd-c768-4317-acf5-68fb4a6bcad4n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-users/c868ec1c-7232-4d86-bdd5-8bc56debaf87n%40googlegroups.com.
