Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Veyon Community Forum

  1. Home
  2. Help & Troubleshooting
  3. Access Control - groups within groups

Access Control - groups within groups

Scheduled Pinned Locked Moved Help & Troubleshooting
4 Posts 2 Posters 239 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gerardsweeney
    wrote on last edited by
    #1

    I'm trying to set up access control.

    I have a Staff user - TomBaker
    He is a Maths teacher in SchoolA

    His AD account membership looks like:
    SchoolA_Teachers_Maths

    SchoolA_Teachers_Maths is a member of a group SchoolA_Teachers
    SchoolA_Teachers is a member of AllSchools_Teachers

    I check the box "Enable usage of Domain groups".
    I add SchoolA_Teachers and/or AllSchools_Teachers to the "Restrict access to members of specific user groups" section.
    I click Apply
    When I run the "test", and put in TomBaker, the account shows it does not have access.

    If I add SchoolA_Teachers_Maths, then it passes.
    So Veyon doesn't appear to understand nested groups.

    I also tried creating a local group on the PC called VeyonUsers, and adding SchoolA_Teachers to that.
    Still didn't pass.

    I thought I could tackle it with "deny" instead, but the pupil accounts are the same nested approach.
    PupilAccount1 - member of SchoolA2020, which is a member of SchoolAPupils

    Is there a way around this?

    If it helps, any..

    Our AD structure is:

    User Accounts
    SchoolA\Staff
    SchoolB\Pupils
    SchoolB\Staff
    SchoolB\Staff

    There will be cases where staff from SchoolA are using PCs in SchoolB.
    So I can't just use a config where SchoolA PCs look at SchoolA\Staff

    1 Reply Last reply
    0
    • T Offline
      T Offline
      tobydox
      wrote on last edited by
      #2

      Hi Gerard,

      unfortunately nested groups are currently not supported. This means you'll have to add allow rules for the individual teacher groups.

      Best regards
      Tobias

      1 Reply Last reply
      0
      • G Offline
        G Offline
        gerardsweeney
        wrote on last edited by
        #3

        Hi..

        I think I'll get round it by using a script to modify the permissions on the Private keyfile on PCs with Master installed.

        In my testing, I've put a PupilAccounts = "Deny read".
        This lets me run the Master as a Teacher, but not as a pupil - which is what I need.

        1 Reply Last reply
        1
        • T Offline
          T Offline
          tobydox
          wrote on last edited by
          #4

          Sounds like a perfect solution!

          1 Reply Last reply
          0

          Powered by NodeBB | Contributors
          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • Users
          • Groups