Jump to: navigation, search

V4/Smart Proxy

(Redirected from V3/Smart Proxy)

Name: V4/Smart Proxy
Incomplete.png Pending review
Last updated: 2015-05-5 by Mkosek


A Smart Proxy is something that the Foreman project uses to add a layer of abstraction to certain operations. One of these is Realm Enrollment.

The IPA Smart Proxy isn't meant to be limited to Foreman, but will provide the features that it needs in order to do provisioning using a one-time password, with little or no user intervention.

The basic steps to do provisioning are:

  1. Create a host
  2. Set an OTP (can be done at host creation)
  3. Pass this OTP to a new host via a kickstart snippet and execute ipa-client-install during the post process.

This can be coupled with more advanced IPA features to do automatic hostgroup assignment based on automember rules. This in turn can let one define sudo and HBAC security by hostgroup, without having to manually assign enrolled hosts.

A Foreman smart proxy must implement a REST API, and that is fine. This REST API is unauthenticated. It will use defined principal to make IPA calls. It is expected that the smart proxy will be installed along side Foreman, and listen only on the localhost port.

Data be returned as JSON.


Other Foreman Smart Proxy APIs can be seen here for reference.

Note I am proposing two namespaces here. One is to match the design principal from Foreman, using /:realm:/:domain and one as a more generic IPA Namespace. I'm open to discarding this second one in favor of one from IPA, but given the nature of these requests I anticipate domain-specific requirements that a generic IPA RESTful API can't provide.

Foreman-specific API

Path REST Type Description Input
/realm/:domain/:fqdn POST Create a host {"hostname": string, "password": string (optional), "random": boolean, "force", boolean}
/realm/:domain/:fqdn DELETE Remove a specific hostgroup

More Generic API

Path REST Type Description Input
/ipa/smartproxy/host GET Get all hosts
/ipa/smartproxy/host/:fqdn GET Retrieve a host entry
/ipa/smartproxy/host/:fqdn POST Create a host entry {"hostname": string, "password": string (optional), "random": boolean, "force", boolean}
/ipa/smartproxy/host/:fqdn DELETE Delete a host entry
/ipa/smartproxy/hostgroup GET Get all host groups
/ipa/smartproxy/hostgroup/:hostgroup GET Get a specific hostgroup
/ipa/smartproxy/hostgroup/:hostgroup POST Create a hostgroup {"cn": string, "description": string}
/ipa/smartproxy/hostgroup/:hostgroup DELETE Delete a specific hostgroup

The return value will be json for all requests.

When a host is created with a random password then the only time that password will be available is in the return value from the creation. It will look something like:

$ curl http://localhost:8090/ipa/rest/host/test18.example.com -X POST --d random=true
  "dn": "fqdn=test18.example.com,cn=computers,cn=accounts,dc=example,dc=com", 
  "fqdn": [
  "has_keytab": false, 
  "has_password": true, 
  "ipauniqueid": [
  "managedby_host": [
  "objectclass": [
  "randompassword": "C5KK=pG6-QBW"


A host in IPA needs to have a valid DNS entry somewhere. If the A record lookup fails then the host will fail to be created unless force = True.

A host can be created with a specific password using the password option, or a random password can be generated setting random to True. If neither is set then a privileged account will be needed to enroll the host.


The current API just manages the creation and deletion, not membership. Membership can be handled using the IPA automember commands but is outside of the scope of this initial implementation.