Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User permission granularity with zones and records #7

Closed
WillyXJ opened this issue Aug 21, 2013 · 5 comments
Closed

User permission granularity with zones and records #7

WillyXJ opened this issue Aug 21, 2013 · 5 comments

Comments

@WillyXJ
Copy link
Owner

@WillyXJ WillyXJ commented Aug 21, 2013

It would be nice to add more granularity to the fmDNS permissions so users can only manage records and zones for a select number of zones rather than all.

For instance, the following zones are hosted by fmDNS:

domain.com
mydomain.com
example.com

UserA only needs access to manage zones domain.com and mydomain.com while UserB only needs to manage the records of example.com.

@ghost ghost assigned WillyXJ Aug 21, 2013
@WillyXJ
Copy link
Owner Author

@WillyXJ WillyXJ commented Aug 28, 2013

This is implemented in 1.0-b13.

Loading

@WillyXJ WillyXJ closed this Aug 28, 2013
@chamambom
Copy link

@chamambom chamambom commented Mar 27, 2015

I am using fmdns 1.3 and facilemanger1.3 , i am trying to get specific users to manage certain zones and records but when i select one zone record ,it restricts all access, can you help

Loading

@WillyXJ
Copy link
Owner Author

@WillyXJ WillyXJ commented Mar 28, 2015

Hi @chamambom,

Would you be able to give me reproducible steps or are you experiencing what was reported in #162?

Thanks.

Loading

@chamambom
Copy link

@chamambom chamambom commented Mar 28, 2015

I saw the case #162 and i saw that the fmdns version is 1.3.3 , and
im running version 1.3 ,is there any difference and do i need update ??

On Sat, Mar 28, 2015 at 4:43 AM, WillyXJ notifications@github.com wrote:

Hi @chamambom https://github.com/chamambom,

Would you be able to give me reproducible steps or are you experiencing
what was reported in #162
#162?

Thanks.


Reply to this email directly or view it on GitHub
#7 (comment).

Loading

@WillyXJ
Copy link
Owner Author

@WillyXJ WillyXJ commented Mar 28, 2015

Yes, always upgrade to the latest version before opening a ticket as they contain bug fixes.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants