Description of problem:
When ipa rpms were upgraded from version 4.2 to 4.4, customized SELinux User
Map is overwritten with some rpm default.  For example, in our environment, in
addition to some mls related users, we put unconfined_u user first in the map
order to give it the least priority.  However, every time we update ipa, our
changes are reset to rpm's default.  We have observed this with the past
versions and also the most current ipa version.
Version-Release number of selected component (if applicable):
IPA 4.4 and previous
How reproducible:
100%
Steps to Reproduce:
1. Have a IPA 4.2 or earlier installed
2. Alter the SELinux user map order using instructions provided at https://acce
ss.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_
Identity_Authentication_and_Policy_Guide/config-selinux.html  to put
unconfined_u first in the order (lowest priority)
3. yum update ipa
4. Observe different map order
Actual results:
Custom SELinux User Map order is changed back to default from the rpm
Expected results:
Custom SELinux User Map order is preserved

dn: cn=ipaConfig,cn=etc,$SUFFIX
add:ipaSELinuxUserMapOrder: guest_u:s0$$xguest_u:s0$$user_u:s0$$staff_u:s0-s0:c0.c1023$$unconfined_u:s0-s0:c0.c1023
add:ipaSELinuxUserMapDefault: unconfined_u:s0-s0:c0.c1023
add:ipaUserObjectClasses: ipasshuser
remove:ipaConfigString:AllowLMhash
add:objectClass: ipaUserAuthTypeClass