On Tue, Oct 18, 2016 at 8:52 AM, Sandro Bonazzola <sbona...@redhat.com>
> On Mon, Oct 17, 2016 at 5:16 PM, Vojtech Szocs <vsz...@redhat.com> wrote:
>> I'm using latest master with some UI patches on top of it.
>> Engine builds OK, however engine-setup does not ask for admin@internal
> Please note that engine-setup is not asking questions you already answered
> in a previous run (answers stored in the post install file).
> Looks like you've been able to set password to None:
> 2016-10-17 17:02:26 DEBUG otopi.context context.dumpEnvironment:770 ENV
>> In $PREFIX/etc/ovirt-engine/engine.conf.d, there is no 11-setup-sso.conf
11-setup-sso.conf file is created only during installation (first
execution of engine-setup with empty db). If it was not created, it means
that you cleared your prefix (by removing existing configuration files),
but you db is not empty and contains old data. Be aware that configuration
files in your prefix and bound to db content, if you clear config files,
you should also clear db content, easiest was is to execute engine-cleanup.
>> AFAIK, this should be done by aaa-jdbc extension, is that correct?
No, 11-setup-sso.conf is part of new SSO feature of 4.0, it's not related
>> (Am I missing something?)
>> Here is how I build Engine:
>> make clean install-dev PREFIX="$PREFIX" \
>> JBOSS_HOME="$engine_jbossHome" \
>> -Dgwt.locale=$engine_gwtLocale -Dgwt.compiler.localWorkers=1" \
>> DEV_BUILD_GWT_DRAFT=$engine_draftCompile \
>> DEV_BUILD_GWT_SUPER_DEV_MODE=$engine_gwtSuperDev \
>> BUILD_GWT_USERPORTAL=$engine_buildUserPortal \
>> BUILD_GWT_WEBADMIN=$engine_buildWebAdmin \
>> Attaching engine-setup log file.
>> Devel mailing list
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> Devel mailing list
Devel mailing list