Gonna try to respond from my email rather than the forum.  My posts keep
being deleted.

The ssh is being initiated using a user in the Jenkins Internal User
Database, not my AD user.  The build is done by another automation
application that calls it using its ssh key (ssh -p 2222
[email protected] command...).  That user is set up in
the internal user database.  This worked fine until Jenkins 2.516.1.  With
this upgrade, we no longer have the checkbox with AD to allow the internal
user database to work also.  From my research it appears that this is
supposed to now be default but I'm not finding that to be the case.  If I
set security realm to internal user database, my ssh succeeds.  If I set it
to AD, it does not.  Any help would be greatly appreciated!  Thanks!

On Thu, Sep 11, 2025 at 8:22 AM 'Björn Pedersen' via Jenkins Users <
[email protected]> wrote:

> Use your user profile (the head icon in the top right). Then under
> security you can add your public keys.
>
> [email protected] schrieb am Montag, 8. September 2025 um 16:42:17 UTC+2:
>
>> 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 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/024b09cb-5b30-4e7a-ba8a-06eea0508969n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/024b09cb-5b30-4e7a-ba8a-06eea0508969n%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/CAByBicbGLqDqWjoc4ffBztJnrt5MQyRHc5R%2Bs5u8OpnfdXJRUg%40mail.gmail.com.

Reply via email to