This issue was migrated from Pagure Issue #3100.Originally filed by ftweedal on 2019-04-29
1) there is an argument order bug in createUserNotice() call sites: the order of noticeText and noticeNums is reversed. This causes failure when you try to define a usernotice policy qualifier.
2) cannot create policies with different numbers of qualifiers. The PolicyQualifiers.num=<int> config applies to all policies, which prevents defining policies with different numbers of
qualifiers.
3) Not a bug per se, but it is necessary to include both CPSURL.enable=<bool> and
usernotice.enable=<bool>, with CPSURL taking precedence. These could default to false, simplifying user configuration a little.
This issue was migrated from Pagure Issue #3100.Originally filed by ftweedal on 2019-04-29
1) there is an argument order bug in
createUserNotice()
call sites: the order ofnoticeText
andnoticeNums
is reversed. This causes failure when you try to define a usernotice policy qualifier.2) cannot create policies with different numbers of qualifiers. The
PolicyQualifiers.num=<int>
config applies to all policies, which prevents defining policies with different numbers of qualifiers.3) Not a bug per se, but it is necessary to include both
CPSURL.enable=<bool>
andusernotice.enable=<bool>
, with CPSURL taking precedence. These could default tofalse
, simplifying user configuration a little.See pki-users thread for background: https://www.redhat.com/archives/pki-users/2019-April/msg00007.html