Error with realm integration with FreeIPA

Problem:
When configuring Smart Proxy with the details for a REALM set up in FreeIPA the host registration results in the error

Failed to create spacewalk.wrasse.internal's realm entry: ERF12-5287 [ProxyAPI::ProxyException]: Unable to create realm entry ([RestClient::BadRequest]: 400 Bad Request) for proxy .....

Expected outcome:
The host should be added to the FreeIPA server

Foreman and Proxy versions:
foreman-1.9.3-1.el7.noarch
foreman-proxy-1.9.3-1.el7.noarch

Foreman and Proxy plugin versions:
foreman-cli-1.9.3-1.el7.noarch
ruby193-rubygem-foreman_setup-3.0.2-1.fm1_9.el7.noarch
foreman-sqlite-1.9.3-1.el7.noarch
foreman-assets-1.9.3-1.el7.noarch
foreman-release-1.9.3-1.el7.noarch
foreman-vmware-1.9.3-1.el7.noarch
foreman-proxy-selinux-1.9.3-1.el7.noarch
foreman-selinux-1.9.3-1.el7.noarch
foreman-installer-1.9.3-1.el7.noarch
foreman-1.9.3-1.el7.noarch
rubygem-hammer_cli_foreman-0.3.0-1.el7.noarch
foreman-compute-1.9.3-1.el7.noarch
foreman-gce-1.9.3-1.el7.noarch
foreman-libvirt-1.9.3-1.el7.noarch
foreman-ovirt-1.9.3-1.el7.noarch
foreman-ec2-1.9.3-1.el7.noarch
foreman-plugin-1.9.3-1.el7.noarch
foreman-release-scl-1-1.el7.x86_64
foreman-debug-1.9.3-1.el7.noarch
foreman-postgresql-1.9.3-1.el7.noarch
foreman-console-1.9.3-1.el7.noarch
foreman-mysql2-1.9.3-1.el7.noarch

Distribution and version:
Centos 7.7

Other relevant data:

FreeIPA server deails:
freeipa-client-common-4.8.4-2.fc31.noarch
freeipa-server-common-4.8.4-2.fc31.noarch
freeipa-client-4.8.4-2.fc31.x86_64
freeipa-server-4.8.4-2.fc31.x86_64
freeipa-server-dns-4.8.4-2.fc31.noarch
freeipa-common-4.8.4-2.fc31.noarch
freeipa-healthcheck-core-0.5-1.fc31.noarch

This looks like the relevant error from the FreeIPA server but I’ve no idea how to resolve it.

==> /var/log/httpd/error_log <==
[Wed Mar 25 14:50:20.873746 2020] [auth_gssapi:error] [pid 117847:tid 139775793121024] [client 10.143.40.10:37892] GSS ERROR In Negotiate Auth: gss_accept_sec_context() failed: [Unspecified GSS failure. Minor code may provide more information ( Request is a replay)], referer: hidden

Foreman 1.9.3 is Ancient - it was released almost 5 years ago. It is very unlikely anyone has a similar working setup and can help you with debugging this issue. There is also a very good chance that if this is a bug in Foreman it has been fixed since then.
It is highly recommend upgrading to a newer, supported version (1.24.1 is the latest at the time of writing, with 2.0 expected to come out in a week or two.

Hi, Thanks for that. Unfortunately when you google foreman install, it gives you the 1.9 manual and I didn’t spot that there were newer versions.

Thanks for pointing that out, looks like we need some bigger warning on the out of date manual pages :slight_smile: