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
  • #5709
Closed
Open
Issue created Oct 04, 2017 by jbecot@jbecotReporter

DNS Tab - record filtering is broken for new systems

Requirements

  • Filling out the template is required. Any Enhancement request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
  • All new code requires tests to ensure against regressions

Descriptive title for this enhancement

Prevent FD to show non related records in the DNS tab

Actual behavior

When you create a system, before saving it with Apply or OK, you can activate the DNS tab and tie the host to a DNS domain. Doing so display non related NS record in the record list, allowing a person who can edit any host to accidently edit another NS record.

Expected behavior

If the hostname is not set yet the list should be empty, or, we should not be able to activate DNS (or DHCP) tab at all

Step by step description of new behaviour

  1. In the system plugin, click on Action > Create new workstation
  2. Before validating it active the DNS tab and tie the machine to a domain

Benefits

It's fairly complicated in our setup to allow limited accounts to add/edit/delete workstations with the ability to generate the NS A record without allowing them to edit the whole zone. The actuel behavior is not satisfying.

Possible Drawbacks

I have no clue of a possible drawback, if you don't allow to activate DNS before saving the machine. One may want to configure every field at the time so this may not be convenient in every scenario.

Enhance display filter by checking if the hostname is not null should not affect other cases.

Applicable Issues

dns_tab_1 dns_tab_2

Edited Nov 02, 2017 by Côme Chilliet
Assignee
Assign to
Time tracking