Restricting API users to certain domains or limiting to one client's resources

Discussion in 'ISPConfig 3 Priority Support' started by kobuki, Oct 30, 2018.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    I can try to take a look at that.
     
  2. kobuki

    kobuki Member HowtoForge Supporter

    Well, in the meantime I've created a small proxy web service that uses the same JSON interface as ISPConfig but uses normal user login credentials for resource checks. It needs a single API user with proper DNS permissions and to read user data for pw hash checks. It allows TXT record access to all of the user's zones. Requires no change to the acme.sh DNS plugin. In case anyone is interested, I can post the source for this.
     
    till likes this.
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Sounds nice until we fully tested and implemented user based out. It would be great if you would post your proxy project, maybe in the addon subforum?
     
  4. kobuki

    kobuki Member HowtoForge Supporter

    Sure, I'll pack it up and post it there later. Or if you see it fits the ISPC GitLab, I can upload a repo there too. Or to GitHub, maybe.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

  6. kobuki

    kobuki Member HowtoForge Supporter

    OK, should I just create a new dir in that repo and put files there?
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes, just a new directory and maybe a short readme text file inside that explains how to use it.
     
  8. kobuki

    kobuki Member HowtoForge Supporter

  9. till

    till Super Moderator Staff Member ISPConfig Developer

    Please make a Merge Request in Gitlab against the master branch of the modules repo with your code, this allows me to 'import' your changes into the main repo.
     
  10. kobuki

    kobuki Member HowtoForge Supporter

    till likes this.

Share This Page