#REQUIRES -Version 2.0 <# Copyright and license info is available in the LICENSE file included with the Server Deployment Package (SDP), and also available online: https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/LICENSE This is an auth-check trigger for Perforce. See detailed comments below for function Is-ADLoginValid #> param ( [string]$user ) <# The following module needs to be installed on the Perforce server machine (where this script will be run by the Perforce server). Download (if necessary), install it and switch on the module. To install, see downloads and instructions: http://blogs.msdn.com/b/rkramesh/archive/2012/01/17/how-to-add-active-directory-module-in-powershell-in-windows-7.aspx Then use Control Panel > Programs and Features > Windows Features Enable the following entry: Remote Server Administration Tools > Role Administration Tools > AD DS and AD LDS Tools > Active Directory Module for Windows PowerShell #> Import-Module ActiveDirectory <# .SYNOPSIS Validates supplied user and password against the current ActiveDirectory server .DESCRIPTION This is intended to be run as a standard Perforce auth-check trigger. It expects the password to be provided on STDIN (Standard input). The username is specified. A typical p4 triggers entry to enable this is: ad-auth-check auth-check auth "powershell -ExecutionPolicy bypass -File c:\triggers\ad-auth-check.ps1 -user %user%" You may need to provide the full pathname to powershell. DON'T FORGET TO RESTART Perforce Service AFTER ADDING NEW TRIGGER!!! Requirements: - ActiveDirectory module noted above - The account under which the Perforce Server Service is running should be in ActiveDirectory (so that default AD server is set). .NOTES File Name : ad-auth-check.ps1 Author : Robert Cowham (rcowham@perforce.com) Prerequisite : PowerShell V2 over Vista and upper. Copyright 2014 - Perforce Software, Inc. See LICENSE.txt for legal information. .LINK Script posted: TBC #> Function Is-ADLoginValid { param ( [String]$user ) [String]$password=$input # The following command uses the currently configured ActiveDirectory server $aduser = Get-ADUser $user -Properties UserPrincipalName Write-Host "Logging in user: "$aduser.UserPrincipalName -NoNewline if ((new-object directoryservices.directoryentry "", $aduser.UserPrincipalName, $password).psbase.name -ne $null) { exit 0 } else { exit 1 } } # Pipe the standard input for the script into the function directly. $input | Is-ADLoginValid -user $user
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 24292 | gmc | "Forking branch Dev of perforce-software-sdp to gmc-sdp." | ||
//guest/perforce_software/sdp/dev/Server/Windows/p4/common/bin/triggers/ad-auth-check.ps1 | |||||
#2 | 16029 | C. Thomas Tyler |
Routine merge to dev from main using: p4 merge -b perforce_software-sdp-dev |
||
#1 | 10961 | C. Thomas Tyler | Merge down from main. | ||
//guest/perforce_software/sdp/main/Server/Windows/p4/common/bin/triggers/ad-auth-check.ps1 | |||||
#1 | 10872 | C. Thomas Tyler |
Added Windows SDP into The Workshop: * Combined (back) into Unix SDP structure. * Avoided adding duplicate files p4verify.pl, p4review.(py,cfg). * Upgraded 'dist.sh' utility to produce both Unix and Windows packages (*.tgz and *.zip), adjusting line endings on text files to be appropriate for Windows prior to packaging. To Do: * Resolve duplication of [template_]configure_new_server.bat. * Merge test suites for Windows and Unix into a cohesive set. |