• This topic is empty.
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #30966

    I am trying to use Powershell to connect to the SOAP API of Cerberus but am stumped on how to do it. All the documentation I see online says I should use the following:


    $CerberusFtpSvc = New-WebServiceProxy -Uri “https://localhost:10001/wsdl/Cerberus.wsdl”

    If I try this I get the error


    The HTML document does not contain Web service discovery information.

    I have tried Credential parameters and Class & Namespace parameters to no avail.

    I have tried different URLs to try and ‘find’ the .wsdl file. (some sites use Files/wsdl/, ive also tried webadmin/admin/wsdl/)

    I think once I get the connection to the SOAP service I should be alright, but I just can’t figure that part out :/





    You may want to access the WSDL and XSD directly on disk and not use the URL.

    It’s in this folder:

    C:Program FilesCerberus LLCCerberus FTP Serverwebadminadminwsdl

    You can always copy that to your local development machine and process it that way.

    The above link has some pretty good information about PowerShell and Cerberus


    Thanks for that, I wasn’t sure if I was doing it right. Knowing I was headed in the right direction helped!

    I was able to connect and then i changed the url property of the new PowerShell object to the server hostname (even if it was run on the local machine).



    $CerberusFtpSvc = New-WebServiceProxy -Uri “C:Program FilesCerberus LLCCerberus FTP ServerwebadminadminwsdlCerberus.wsdl” -Class CerberusFtp -Namespace CerberusFTPService -Credential $Cred
    $CerberusFtpSvc.Url = ‘https://:10001/service/cerberusftpservice’

    After this everything else fell into place.

    $Cred = The SOAP Admin Username/Password as a Powershell object, i.e.:


    $cred = Get-Credential

    I am now navigating around the many property and methods available to me.

    Thanks again.


    I’ve managed to get quite far with the SOAP API which is great however I have hit a road block:

    I am not sure if the API can manipulate AD Users.

    I am trying to assign Cerberus Groups to AD Users, but cannot find any way to list AD Users or their group assignments.

    I don’t think it’s possible which is a massive bummer!



    Managing Active Directory (AD) and LDAP users work very differently and aren’t easily done at this time using the SOAP API.

    AD and LDAP users are authenticated directly against their respective AD and LDAP server using the default configuration specified on the AD Users and LDAP Users pages. They don’t exist as user accounts in Cerberus.

    You can customize individual AD and LDAP users by mapping them in the Cerberus UI to a Cerberus group. That would override the default AD or LDAP configuration and apply the settings and virtual directories from that mapped Cerberus group to the AD user.

    We don’t have a SOAP API call to manage these mappings at this time. There are only the GetAuthenticationList and SetAuthenticationList calls that retrieve an XML block of those sources and mappings. Our application can easily manipulate that data, but it would have to be parsed and manipulated at the XML level by an API user.

    We have plans to add individual APIs to manage mapping AD and LDAP users to Cerberus groups through the API, but those calls aren’t in place yet.

    I wish I had a better answer for you. It’s certainly possible using the XML set and retrieval methods, but not at all ideal.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.