Remote Execution public key

Support
1

Built my test rig with the latest Katello 3.2 release and looking into the
Remote Execution plugin. I can get it working by manually copying the .pub
key into the client's authorized_keys file, but I'm not seeing the key
published via the API as is claimed in the manual:

https://theforeman.org/plugins/foreman_remote_execution/0.3/index.html#2.2RemoteHostsConfiguration

claims

curl https://myproxy.example.com:8443/ssh/pubkey >> ~/.ssh/authorized_keys

is a method for pulling the relevant key onto the host. But I get nothing
back from that URL and can find nothing in the API docs about pubkey. Has
this method been dropped?

Cheers

D

2

Looking at recently installed machine I can see that the default https port
for smart proxy was changed from 8443 to 9090, check which port your proxy
should listen on with cat /etc/foreman-proxy/settings.yml | grep https_port.

Hope this helps

Adam

··· On Wed, Nov 16, 2016 at 12:51 PM, Duncan Innes wrote:

Built my test rig with the latest Katello 3.2 release and looking into the
Remote Execution plugin. I can get it working by manually copying the .pub
key into the client’s authorized_keys file, but I’m not seeing the key
published via the API as is claimed in the manual:

Foreman :: Plugin Manuals.
2RemoteHostsConfiguration

claims

curl https://myproxy.example.com:8443/ssh/pubkey >> ~/.ssh/authorized_keys

is a method for pulling the relevant key onto the host. But I get nothing
back from that URL and can find nothing in the API docs about pubkey. Has
this method been dropped?

Cheers

D

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

3

Bingo - 9090 it is. I'll submit a change for the documentation.

··· On Wednesday, 16 November 2016 12:03:38 UTC, Adam Ruzicka wrote: > > Looking at recently installed machine I can see that the default https > port for smart proxy was changed from 8443 to 9090, check which port your > proxy should listen on with cat /etc/foreman-proxy/settings.yml | grep > https_port. > > Hope this helps > > Adam > > On Wed, Nov 16, 2016 at 12:51 PM, Duncan Innes > wrote: > >> Built my test rig with the latest Katello 3.2 release and looking into >> the Remote Execution plugin. I can get it working by manually copying the >> .pub key into the client's authorized_keys file, but I'm not seeing the key >> published via the API as is claimed in the manual: >> >> >> https://theforeman.org/plugins/foreman_remote_execution/0.3/index.html#2.2RemoteHostsConfiguration >> >> claims >> >> curl https://myproxy.example.com:8443/ssh/pubkey >> >> ~/.ssh/authorized_keys >> >> is a method for pulling the relevant key onto the host. But I get >> nothing back from that URL and can find nothing in the API docs about >> pubkey. Has this method been dropped? >> >> Cheers >> >> D >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> > >
4

Sorry to revive this old thread but the documentation still says port 8443 and port 9090 is the port that works.-> Foreman :: Plugin Manuals
Can someone update the documentation?

1 Like
5

Well, the thing is, 8443[1] is the port if you don’t have katello. In the katello scenario the default port moves to 9090[2]. And nothing prevents you from using something completely different.

Also the new docs have this covered properly in Foreman - Managing Hosts and Katello - Managing Hosts

[1] - puppet-foreman_proxy/init.pp at 1e45b6b47cf9357f15dd16a41b241403d480b537 · theforeman/puppet-foreman_proxy · GitHub
[2] - foreman-installer/katello-answers.yaml at develop · theforeman/foreman-installer · GitHub