Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory-plugins fusiondirectory-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectory-pluginsfusiondirectory-plugins
  • Issues
  • #5441
Closed
Open
Issue created Mar 16, 2017 by Côme Chilliet@cchillietReporter

Allow notify option does not match what it does

Hello,

There is «Allow notify» checkbox in FD ldap2zone service, which is LDAP attribute argonautLdap2zoneAllowNotify, but what it actually does is set «notify» option in the zone. You can see here that notify and allow-notify are not the same thing: http://www.zytrax.com/books/dns/ch7/xfer.html#notify

I think we should rename the option, and maybe even the LDAP attribute as it makes no sense to store AllowNotify as a boolean anyway.

(from redmine: issue id 5441, created on 2017-03-16, closed on 2017-04-12)

  • Relations:
    • copied_to #5438 (closed)
  • Changesets:
    • Revision 45704950 by Côme Chilliet on 2017-03-23T10:34:21.000Z:
Fixes #5441 Added Notify instead of Allow Notify as SelectAttribute
  • Custom Fields:
    • Bug in version: 1.0.19
    • Support contract: None
Assignee
Assign to
Time tracking