On 03/17/2011 10:01 PM, Endi Sukma Dewata wrote:
On 3/17/2011 7:04 PM, Adam Young wrote:
Some issues:
1. There's a jslint warning.
2. Try creating a new password policy, then edit and change the
priority. When you click Update the priority will get updated but the
field will become read
On 3/18/2011 8:57 AM, Adam Young wrote:
On 03/17/2011 10:01 PM, Endi Sukma Dewata wrote:
On 3/17/2011 7:04 PM, Adam Young wrote:
Some issues:
1. There's a jslint warning.
2. Try creating a new password policy, then edit and change the
priority. When you click Update the priority will get
On 03/18/2011 10:43 AM, Endi Sukma Dewata wrote:
On 3/18/2011 8:57 AM, Adam Young wrote:
On 03/17/2011 10:01 PM, Endi Sukma Dewata wrote:
On 3/17/2011 7:04 PM, Adam Young wrote:
Some issues:
1. There's a jslint warning.
2. Try creating a new password policy, then edit and change the
From d8c6d615a87a9f8d06260ad06d4caec6ddd55526 Mon Sep 17 00:00:00 2001
From: Adam Young ayo...@redhat.com
Date: Thu, 17 Mar 2011 19:52:52 -0400
Subject: [PATCH] pwpolicy priority
Priority is now a required field in order to add a new password policy. Thus, not having the field present means we
On 3/17/2011 7:04 PM, Adam Young wrote:
Some issues:
1. There's a jslint warning.
2. Try creating a new password policy, then edit and change the
priority. When you click Update the priority will get updated but the
field will become read only.
