We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Active Directory Sample Clauses

Active DirectoryAgency Data Users will need an SFDPH Active Directory account in order to access each System(s). These Active Directory Accounts will be created as part of the provisioning process.
Active DirectoryFor products that support Active Directory capability, Customer will provide integrated Active Directory services and user administration, e.g., passwords, user log-in, etc.
Active Directory. Domain functional Level of the CAH domain are set to “Windows Server 2016”. Kerberos is primarily used for user authentication in ActiveDirectory. The use of LM and NTLM is prohibited. NTLMv2 can be used with approval by ED/ICT and Ř /IBE. When using Basic authentication, it is necessary to use an encrypted connection, see the “Authentication” section. The application must not require any permission in Active Directory beyond a routine user account in a routine operation.
Active Directory. Services Creating, modifying and removing objects (such as users\groups\organizational units\group policy objects) Service Request Yes
Active Directory. Capture and monitor detailed Service Desk records and analyse information, taking preventative action to ensure Service Levels are met and recommending service improvements.
Active Directory. 3.1 The Army Enterprise Network Operations (NetOps) Integrated Architecture (AENIA) Requirements Document (ARD) For Active Directory Services Management. 15 August 2007, (requires AKO Login). xxxxx://xxx.xx.xxxx.xxx/suite/doc/13985332 3.2 Request, Approval, and Implementation of Active Directory Trusts within the Army Enterprise Infostructure (AEI) – TECHCON 2004-015A. 7 February 2006, (Requires AKO Login) xxxxx://xxx.xx.xxxx.xxx/suite/doc/7405333 3.3 Active Directory Management Roles and Responsibilities – TECHCON 2004-008, 29 March 2005, xxxxx://xxx.xx.xxxx.xxx/suite/doc/6736262
Active Directory. IV.9.1.1 Domain functional Level of LP domain is set to “Windows Server 2008 R2” IV.9.1.2 For user authentication in ActiveDirectory, the Kerberos protocol is preferred. Use of LM and NTLM is prohibited. With approval by CEO/ICT, it is also acceptable to use NTLMv2. If Basic authentication is used, the connection must be encrypted. IV.9.1.3 During routine operation, the application must not require any permissions in Active Directory out of scope of a normal user account.
Active Directory. Barcode Scanning Solution must offer integration with City’s Active Directory to authenticate System Users. Yes This is a key functionalities within the Visium Platform. 5.02 5.03 external parties (within diverse authentication settings such as knowledge‐based or credential‐based) included but not limited to PIN code, third party authentication like OATH/XXXX, phone #, email, etc.
Active Directory. This Section details the obligations and responsibilities of the Parties regarding Active Directory management with respect to the Infrastructure Services. Except where a responsibility is identified as a “P” responsibility for CoreLogic in the matrix below, Supplier shall be responsible for the associated activities. Supplier shall: 1.2.4.1 Manage Active Directory in support of the Services. P 1.2.4.2 Monitor Active Directory replication and configuration between sites and raise alerts in the ITSM System (e.g., alerts relating to issues with performance, Active Directory Objects and replication). P 1.2.4.3 Install, configure, maintain, troubleshoot and secure domain controllers. P 1.2.4.4 Design, configure and support Microsoft Operating System Software Active Directory integrated DNS Services. P A 1.2.4.5 Manage and maintain the Active Directory forest, domains, and OU structure. P 1.2.4.6 Design, build, configure and support global, local and individual group policy objects. P A 1.2.4.7 Maintain security and maintenance best practices in alignment with CoreLogic’s standards and best practices. P 1.2.4.8 Design, configure and support public key Infrastructure within Active Directory. P A 1.2.4.9 Design, configure and support of Windows Time service, domain and forest trusts, global catalogs, and domain controllers. P A
Active Directory. This will be an integration to the Customer’s local or Azure active directory service using Federated services. This integration will enable Customer users of the NICE Justice SaaS Solution to authenticate using their active directory credentials and NICE may also use AD groups to configure users with group and role-based permissions within the Justice SaaS Solution for access control purposes.