On 11/27/2012 04:48 PM, Endi Sukma Dewata wrote:
On 11/20/2012 10:46 AM, Petr Vobornik wrote:
I think that ipaexternalmember, gidnumber and macaddress attributes
might cause trouble as well. They are all in objectclasses that are
added to objects on-demand (like ipasshuser/ipasshhost is).
On 11/20/2012 10:46 AM, Petr Vobornik wrote:
I think that ipaexternalmember, gidnumber and macaddress attributes
might cause trouble as well. They are all in objectclasses that are
added to objects on-demand (like ipasshuser/ipasshhost is).
Honza
Thanks for the catch. There is a problem with
Hi,
On 19.11.2012 13:38, Petr Vobornik wrote:
After upgrade, sshkeys of existing users and hosts are not editable
because attribute level rights are not send to Web UI due to lack of
ipasshuser object class.
'w_if_no_aci' attribute flag was introduced to bypass this issue. It
makes attribute
On 11/20/2012 10:48 AM, Jan Cholasta wrote:
Hi,
On 19.11.2012 13:38, Petr Vobornik wrote:
After upgrade, sshkeys of existing users and hosts are not editable
because attribute level rights are not send to Web UI due to lack of
ipasshuser object class.
'w_if_no_aci' attribute flag was
After upgrade, sshkeys of existing users and hosts are not editable
because attribute level rights are not send to Web UI due to lack of
ipasshuser object class.
'w_if_no_aci' attribute flag was introduced to bypass this issue. It
makes attribute writable when AttributeLevelRights are not
On 11/19/2012 6:38 AM, Petr Vobornik wrote:
After upgrade, sshkeys of existing users and hosts are not editable
because attribute level rights are not send to Web UI due to lack of
ipasshuser object class.
'w_if_no_aci' attribute flag was introduced to bypass this issue. It
makes attribute
