I have a problem whit the syntax of the nsViewFilter attribute, the value of the attribute is: (ou=*ou=D. PERIÓDICO,o=xxxxx,dc=xxxx,dc=xxxx). I guess the problem is the character "Ó" but if it is possible to create the ou with special characters, should be possible create a nsViewFilter with special characters to??? (389DS 1.2.5)
Noriko Hosoi says:
Currently, the syntax of nsViewFilter is IA5 String, which does not allow non-ascii characters.
attributeTypes: ( 2.16.840.1.113722.214.171.12423 NAME 'nsViewFilter' DESC 'Netscape defined attribute type' SYNTAX 126.96.36.199.4.1.14188.8.131.52.26 X-ORIGIN 'Netscape Directory Server' )
Indeed, it'd be a needless restriction for nsViewFilter. Please open a ticket at https://fedorahosted.org/389/newticket.
In the meantime, could you replace 184.108.40.206.4.1.14220.127.116.11.26 with 18.104.22.168.4.1.1422.214.171.124.15, and try?
I have replaced the syntax as said and now there is not syntax error.
attributeTypes: ( 2.16.840.1.1137126.96.36.19923 NAME 'nsViewFilter' DESC 'Netscape defined attribute type' SYNTAX 188.8.131.52.4.1.14184.108.40.206.15 X-ORIGIN 'Netscape Directory Server' )
set default ticket origin to Community
Added initial screened field value.
git merge ticket349
ldap/schema/02common.ldif | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
git push origin master
Enter passphrase for key '/home/lkrispen/.ssh/id_rsa_fedora':
Counting objects: 9, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 711 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
ecbd8b7..da4e868 master -> master
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=918698
Metadata Update from @mbarper:
- Issue assigned to lkrispen
- Issue set to the milestone: 1.3.0.rc1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
to comment on this ticket.