Description of problem:

ovirt-engine-extension-aaa-ldap-setup asks an user to "specify profile name thta will be visible to users" and then it invisibly appends to such name '-authz' behind the scene.

this causes SSO to Windows guest does not work by default as engine "sends" not domain but domain + '-authz' in VM.desktopLogin. very odd for a sysadmin who configured this domain for SSO for Windows guests' client users.

# ovirt-engine-extension-aaa-ldap-setup 
[ INFO  ] Stage: Initializing
[ INFO  ] Stage: Environment setup
          Configuration files: ['/etc/ovirt-engine-extension-aaa-ldap-setup.conf.d/10-packaging.conf']
          Log file: /tmp/ovirt-engine-extension-aaa-ldap-setup-20160506150259-66hevw.log
          Version: otopi-1.4.1 (otopi-1.4.1-1.el6ev)
[ INFO  ] Stage: Environment packages setup
[ INFO  ] Stage: Programs detection
[ INFO  ] Stage: Environment customization
          Welcome to LDAP extension configuration program
          Please specify profile name that will be visible to users: ad-w2k8r2.example.com
^^^^^^^^^^^^^^^^^^^^^ provided by admin
...
          2016-05-06 15:04:00 INFO    ========================================================================
          2016-05-06 15:04:00 INFO    ============================== Execution ===============================
          2016-05-06 15:04:00 INFO    ========================================================================
          2016-05-06 15:04:00 INFO    Profile='ad-w2k8r2.example.com' authn='ad-w2k8r2.example.com-authn' authz='ad-w2k8r2.example.com-authz' mapping='null'
                                                      ^^^^^^ addition
          2016-05-06 15:04:00 INFO    API: -->Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS user='ad-w2k8r2'
          2016-05-06 15:04:00 INFO    API: <--Authn.InvokeCommands.AUTHENTICATE_CREDENTIALS result=SUCCESS
          2016-05-06 15:04:00 INFO    --- Begin AuthRecord ---
          2016-05-06 15:04:00 INFO    AAA_AUTHN_AUTH_RECORD_PRINCIPAL: ad-w2k8r2.com
          2016-05-06 15:04:00 INFO    --- End   AuthRecord ---
          2016-05-06 15:04:00 INFO    API: -->Authz.InvokeCommands.FETCH_PRINCIPAL_RECORD principal='ad-w2k8r2.com'
          2016-05-06 15:04:00 INFO    API: <--Authz.InvokeCommands.FETCH_PRINCIPAL_RECORD status=SUCCESS
          2016-05-06 15:04:00 INFO    --- Begin PrincipalRecord ---
          2016-05-06 15:04:00 INFO    AAA_AUTHZ_PRINCIPAL_DISPLAY_NAME: ad-w2k8r2
          2016-05-06 15:04:00 INFO    AAA_AUTHZ_PRINCIPAL_PRINCIPAL: ad-w2k8r2.com
          2016-05-06 15:04:00 INFO    AAA_LDAP_UNBOUNDID_DN: CN=ad-w2k8r2,CN=Users,DC=ad-w2k8r2,DC=example,DC=com
          2016-05-06 15:04:00 INFO    AAA_AUTHZ_PRINCIPAL_ID: KqAXTzGX9UaxSaIuawL4ug==
          2016-05-06 15:04:00 INFO    AAA_AUTHZ_PRINCIPAL_NAME: ad-w2k8r2
          2016-05-06 15:04:00 INFO    AAA_AUTHZ_PRINCIPAL_FIRST_NAME: ad-w2k8r2
          2016-05-06 15:04:00 INFO    AAA_AUTHZ_PRINCIPAL_NAMESPACE: DC=ad-w2k8r2,DC=example,DC=com
          2016-05-06 15:04:00 INFO    --- End   PrincipalRecord ---



jsonrpc.Executor/7::DEBUG::2016-05-06 15:19:49,529::__init__::503::jsonrpc.JsonRpcServer::(_serveRequest) Calling 'VM.desktopLogin' in bridge with {u'username': u'ad-w2k8r2', u'domain': u'ad-w2k8r2.example.com-authz', u'password': '********', u'vmID': u'ed875d98-
                       ^^^^^^ such domain does not exist

e407-4b07-967a-363cbecf3bb3'}

Version-Release number of selected component (if applicable):
ovirt-engine-extension-aaa-ldap-setup-1.1.4-1.el6ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. configure an AD via ovirt-engine-extension-aaa-ldap-setup, provide exact
   domain name for profile name to be visible by users
2. assing a VM to an AD user
3. open User Portal as the AD user and open console
4. observe vdsm.log for VM.desktopLogin line and value of domain sent

Actual results:
ovirt-engine-extension-aaa-ldap-setup appends '-authz' invisibly and this causes engine to send not exact AD domain which was configured to VM.desktopLogin action; thus SSO does not work as domain is wrong

Expected results:
ovirt-engine-extension-aaa-ldap-setup should not append any string to user provided "names" for domains

Additional info:
renaming config files is not user friendly and understanding aaa config files seems to be rocket science, thus ovirt-engine-extension-aaa-ldap-setup should create configuration which works by default