Technical (infrastructure) configuration of midPoint deployment.

Item Summary
Name	Type	Multiplicity	Description
defaultHostname	property string	[0,1]	Hostname that will be used as a public hostname for the midPoint deployment.
intraClusterHttpUrlPattern	property string	[0,1]	Pattern for HTTP/HTTPS communication inside midPoint cluster.
remoteHostAddressHeader	property string	[0,-1]	Whether to try to determine client's IP address information from HTTP headers and if so, what header(s) to use.
publicHttpUrlPattern	property string	[0,1]	Pattern for HTTP/HTTPS communication with client.

Items
- defaultHostname
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Hostname that will be used as a public hostname for the midPoint deployment. E.g. it will be used in URLs that point to the midPoint in notification mails.
- intraClusterHttpUrlPattern
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Pattern for HTTP/HTTPS communication inside midPoint cluster. This is specifies the URLs that ure used by midPoint cluster nodes when they need to communicate with each other. The pattern is in fact an URL prefix pointing to root URL of the application. Specific paths will be appended to the URL. Example: https://$host/midpoint
- remoteHostAddressHeader
  
  Flags: RAM,runtime
  
  Multiplicity: [0,-1]
  
  Whether to try to determine client's IP address information from HTTP headers and if so, what header(s) to use. Note that the order of headers to try is indeterminate: they might be tried in any order.
- publicHttpUrlPattern
  
  Flags: RAM,runtime
  
  Multiplicity: [0,1]
  
  Pattern for HTTP/HTTPS communication with client. This specifies the URL that is used by midPoint when it creates redirect URL for client. The pattern is in fact an URL prefix pointing to root URL of the application. Specific paths will be appended to the URL. Example: 'https://$host/midpoint', where 'defaultHostname' element is used as '$host'.