• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 65 subscribers
  • Views 3700 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARS 7.2 - can the web interface be managed by groups?

ldandridge
over 6 years ago

i.e.  In our previous install we only used the ARWebAdmin WI for both our Admins and Helpdesk and controlled access through group memberships. The old server, version 6.9, is still functioning so if someone can tell me where this would have been configured so I can compare and duplicate the settings on our new servers I'd appreciate it.

       We did import the current configuration to the new version and our modified templates came over. Now our helpdesk users can see and use the CONFIGURATION menu option on the WI and I can't find the spot to make my changes.

      Any help will be appreciated.

leed

  • 0 over 6 years ago
    not sure about the questions.
    #1. Access Templates (AT) is the right way to control access to AD in ARS via AD\groups (virtaul permissions/roles)
    #2. ARS WI layout allows to be configured in general, or per OU (scope) and other ldap criteria. It is *layout* and should not be confused and used as #1. *permissions*.
    #3. Separate Websites http://ARSADMins, http://ARSHelpDesk - very common practice, when website configuration customized per website dedicated to AD\group (AD\HelpDesk is denied to access http://ARADMins on IIS/website level)
  • 0 over 6 years ago
    is there a specific set of templates that control the web interface?
  • 0 over 6 years ago

    My understanding.
    AT controls delegation/permissions on Server side ("virtual ACL").
    Client can be: ARS MMC, ARS WI, Script (PS1, VBS etc.), SPML. ("Layout and Presentation layer")
    Client is not Permission.

  • 0 over 6 years ago

    Another thing to add is there are visibility options in the presentation of the Web Interface, although this does not prevent users from performing the action using the ADSI Provider, PSProvider, SPML etc.. Best Suggestion is to always use Access Templates as Aidar Pointed out in that no matter what Provider/Interface it is valid.