Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
2,274
Downloads of v 2.0.0.19:
1,254
Last Update:
02 Jan 2015
Package Maintainer(s):
Software Author(s):
- Apache
Tags:
ldap kerberos server apache apacheds- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

ApacheDS
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
2,274
Downloads of v 2.0.0.19:
1,254
Maintainer(s):
Software Author(s):
- Apache
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
Some Checks Have Failed or Are Not Yet Complete
1 Test Unknown and 1 Failing Test
To install ApacheDS, run the following command from the command line or from PowerShell:
To upgrade ApacheDS, run the following command from the command line or from PowerShell:
To uninstall ApacheDS, run the following command from the command line or from PowerShell:
NOTE: This applies to both open source and commercial editions of Chocolatey.
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download apacheds --internalize --source=https://community.chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://community.chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade apacheds -y --source="'STEP 3 URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade apacheds -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Ensure apacheds installed
win_chocolatey:
name: apacheds
state: present
version: 2.0.0.19
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'apacheds' do
action :install
version '2.0.0.19'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: apacheds,
Version: 2.0.0.19,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller apacheds
{
Name = 'apacheds'
Ensure = 'Present'
Version = '2.0.0.19'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'apacheds':
provider => 'chocolatey',
ensure => '2.0.0.19',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install apacheds version="2.0.0.19" source="STEP 3 URL"
See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.
5. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator ferventcoder on 03 Jan 2015.
ApacheDS is a LDAP and Kerberos server. It is possible to connect to this server by using Apache Directory Studio
and connecting to localhost port 10389
, username uid=admin,ou=system
and password secret
.
Optional installation commands:
Issue -packageparameters '"/InstallLocation=C:\Path\to\installationdirectory"'
to overwrite the default installation directory, e.g. choco install apacheds -packageparameters '"/InstallLocation=C:\temp"'
extracts the package in C:\temp
.
Bugs and Features:
Create an issue or comment to an existing one - https://github.com/030/chocolateyautomatic/issues
$packageName = 'apacheds'
$Url = 'http://apache.hippo.nl/directory/apacheds/dist//2.0.0-M19/apacheds-2.0.0-M19.zip'
$global:installLocation = "C:\ApacheDS"
$checksum = '03c5015bb9a59b9b2e560db7e331d794'
$checksumType = 'md5'
if(!$PSScriptRoot){ $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent }
. "$PSScriptRoot\OverwriteParameters030.ps1"
. "$PSScriptRoot\Install-ChocolateyService030.ps1"
OverwriteParameters030
Install-ChocolateyZipPackage "$packageName" "$Url" "$global:installLocation" -checksum "$checksum" -checksumType "$checksumType"
$packageVersion = (gci "$global:installLocation\apacheds-*\").FullName -replace ".*apacheds-" | sort -Descending | Select -first 1
$apachedsHome = "${global:installLocation}\apacheds-${packageVersion}"
Install-ChocolateyService030 "apacheds" "ApacheDS" "nssm install ApacheDS `"java`" -jar `"${apachedsHome}\lib\apacheds-service-${packageVersion}.jar`" `"${apachedsHome}\instances\default-$packageVersion`"" "10389"
$packageName = 'apacheds'
if(!$PSScriptRoot){ $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent }
. "$PSScriptRoot\Install-ChocolateyService030.ps1"
. "$PSScriptRoot\Uninstall-ChocolateyZipPackage030.ps1"
Uninstall-ChocolateyService030 "$packageName"
Uninstall-ChocolateyZipPackage030 "$packageName"
function Install-ChocolateyService030 {
<#
.SYNOPSIS
Installs a service
.DESCRIPTION
This will install a service
.PARAMETER PackageName
The name of the package for whom the service will be installed.
.PARAMETER ServiceName
The name of service which will be used to install and start the service.
.PARAMETER CreateServiceCommand
The command which installs the service.
.PARAMETER AvailablePort (OPTIONAL)
The port which needs to be available in order to start the service.
.EXAMPLE
Install-ChocolateyService030 'PACKAGE_NAME' 'SERVICE_NAME' 'INSTALL_COMMAND' 'PORT'
Install-ChocolateyService030 "dcm4chee" "DCM4CHEE" "nssm install DCM4CHEE `"java`" -jar `"%DCM4CHEE_HOME%/bin/run.jar"`" "8090"
Install-ChocolateyService030 "postgresqlzip" "PostgreSQL" "pg_ctl register -N `"PostgreSQL`" -U `"LocalSystem`" -w" "5432"
Install-ChocolateyService030 "apacheds" "ApacheDS" "nssm install ApacheDS `"java`" -jar `"%APACHEDS_HOME%/lib/apacheds-service-${version}.jar`" `"%APACHEDS_HOME%/instances/default`"" "10389"
Install-ChocolateyService030 "test" "test" "nssm install test `"$testDirectory\testService.bat`""
.OUTPUTS
None
.NOTES
This helper reduces the number of lines one would have to write to install a service to 1 line.
This method has error handling built into it.
.LINK
UnInstall-ChocolateyService030
Get-ServiceExistence
#>
param(
[string] $packageName,
[string] $serviceName,
[string] $createServiceCommand,
[int] $availablePort
)
Write-debug "Running 'Install-ChocolateyService030' for $packageName with serviceName:`'$serviceName`', createServiceCommand: `'$createServiceCommand`', availablePort: `'$availablePort`' ";
if (!$packageName) {
Write-ChocolateyFailure "Install-ChocolateyService030" "Missing PackageName input parameter."
return
}
if (!$serviceName) {
Write-ChocolateyFailure "Install-ChocolateyService030" "Missing ServiceName input parameter."
return
}
if (!$createServiceCommand) {
Write-ChocolateyFailure "Install-ChocolateyService030" "Missing CreateServiceCommand input parameter."
return
}
Uninstall-ChocolateyService030 -serviceName "$serviceName"
if ($availablePort -and (Get-StatePort)) {
Write-ChocolateyFailure "Install-ChocolateyService030" "$availablePort is in LISTENING state and not available."
return
}
try {
Write-Host "$packageName service will be installed"
iex $createServiceCommand
} catch {
Write-ChocolateyFailure "Install-ChocolateyService030" "The createServiceCommand is incorrect: '$_'."
return
}
if (Get-ServiceExistence030) {
Write-Host "$packageName service will be started"
for ($i=0;$i -lt 12; $i++) {
$serviceStatus = Get-Service -Name $serviceName
start-service $serviceName
if (($serviceStatus.Status -eq "running") -and (Get-StatePort)) {
Write-Host "$packageName service has been started"
return
} else {
Write-Host "$packageName service cannot be started. Attempt $i to start the service."
}
if ($i -eq 11) {
Write-ChocolateyFailure "Install-ChocolateyService030" "service $serviceName cannot be started."
return
}
Start-Sleep -s 10
}
} else {
Write-ChocolateyFailure "Install-ChocolateyService030" "service $serviceName does not exist."
return
}
}
function Get-ServiceExistence030 {
param(
[string] $serviceName = $serviceName
)
Get-WmiObject -Class Win32_Service -Filter "Name='$serviceName'"
}
function Uninstall-ChocolateyService030 {
param(
[string] $serviceName = $serviceName
)
$service = Get-ServiceExistence030 -serviceName $serviceName
if ($service) {
Write-Host "$serviceName service already exists and will be removed"
stop-service $serviceName
$service.delete()
}
}
function Get-StatePort {
return Get-NetTCPConnection -State Listen | Where-Object {$_.LocalAddress -match "::|0.0.0.0" -and $_.LocalPort -eq "$availablePort"}
}
function OverwriteParameters030 {
$arguments = @{};
$packageParameters = $env:chocolateyPackageParameters;
if($packageParameters) {
$MATCH_PATTERN = "/([a-zA-Z]+)=([`"'])?(.*)([`"'])?"
$PARAMATER_NAME_INDEX = 1
$VALUE_INDEX = 3
if($packageParameters -match $MATCH_PATTERN){
$results = $packageParameters | Select-String $MATCH_PATTERN -AllMatches
$results.matches | % {
$arguments.Add(
$_.Groups[$PARAMATER_NAME_INDEX].Value.Trim(),
$_.Groups[$VALUE_INDEX].Value.Trim())
}
}
if($arguments.ContainsKey("InstallLocation")) {
$global:installLocation = $arguments["InstallLocation"];
Write-Host "Value variable installLocation changed to $global:installLocation"
}
}
}
function Uninstall-ChocolateyZipPackage030 {
param(
[string] $packageName
)
if(!$packageName) {
Write-ChocolateyFailure "Uninstall-ChocolateyZipPackage030" "Missing PackageName input parameter."
return
}
ChildItem "$env:ChocolateyInstall\lib\${packageName}.*" -Recurse -Filter "${packageName}Install.zip.txt" |
ForEach-Object{ $installLocation = (Get-Content $_.FullName | Select-Object -First 1);
if (("$installLocation" -match "${packageName}|adt-bundle-windows-x86_64") -and (Test-Path -Path "$installLocation")) {
Write-Host "Uninstalling by removing directory $installLocation";
Remove-Item -Recurse -Force "$installLocation"
}
}
}
Log in or click on link to see number of positives.
- apacheds.2.0.0.19.nupkg (9db740a3d2d3) - ## / 56
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version | Downloads | Last Updated | Status |
---|---|---|---|
ApacheDS 2.0.0.19 | 1254 | Friday, January 2, 2015 | Approved |
Ground Rules:
- This discussion is only about ApacheDS and the ApacheDS package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or ApacheDS, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.