Description of problem:
Since schema is static varibale, it's not possible to use more different values 
for it. The last one wins, and it's not possible to use other profiles, which use
different schema name.

Version-Release number of selected component (if applicable):
ovirt-engine-extension-aaa-jdbc-0.0.0-4.el6ev.noarch

How reproducible:
always

Steps to Reproduce:
1. Create two profiles, each with diffrent schema name
2. restart engine
3. Check which profile was loaded as first one
4. try to login to this profile

Actual results:
Fail to login.


Expected results:
Succed to login.

Additional info:
2015-08-14 12:51:09,204 TRACE [org.ovirt.engine.extension.aaa.jdbc.core.datasource.Sql] (ajp-/127.0.0.1:8702-2) [] cursor for: SELECT uuid, name, value, description FROM public.settings;

2015-08-14 12:51:09,208 DEBUG [org.ovirt.engine.extension.aaa.jdbc.binding.api.AuthnExtension] (ajp-/127.0.0.1:8702-2) [] Exception:: org.postgresql.util.PSQLException: ERROR: relation "public.settings" does not exist
  Position: 44


It always uses the schema name of profile, which is loaded as last one.