Approve Account Request via SOAP

Comments

3 comments

  • Official comment
    Avatar
    Ian Butteriss

    Hello! Thanks for your interest in Cerberus.

    We don't have a high-level API for this specific operation, unfortunately. However, using a combination of operations, it can be done. If you want to approve account requests via the SOAP API, you would have to do the following:
     
    1. Get the list of currently requested accounts (GetRequestedAccounts)
    2. Pick the one you want to approve
    3. Create a new user out of the details provided in the request
    4. Add the user using SOAP API (AddUser)
    5a. If successful, remove the corresponding account request from the requested accounts XML, and SetRequestedAccounts with the set of requests retrieved in step 1, minus the approved one
    5b. If unsuccessful, reply with some kind of error and leave the requested accounts list unmodified
     
    This emulates what we do in our user interface. If you have further questions, feel free to reach out to us at support@cerberusftp.com.
     
    Thanks,
    Ian Butteriss
    Cerberus Support
    Comment actions Permalink
  • Avatar
    JW3153

    Thanks Ian

    I think this will work fine for our needs. I will disucss with the team today and play a bit more with the trial version and go from there.

    One final question though, it looks like GetRequestedAccountsResponse only returns an XML object and is not mapped to an actual object like the other xxxResponse methods.

    For example GetUserInformationResponse returns a UserInformation object that has all properties from a User, yet GetRequestedAccountsResult only seems to return XML with no access to any of the RequestedAccount properties. Is this correct? Why would it be different to all the other methods?

    0
    Comment actions Permalink
  • Avatar
    Ian Butteriss

    Sorry for the delay in replying to your question.

    There are other Result messages that have only XML blocks. They are low level soap API we have not created high-level interfaces for.
     
    It is correct. It is just one among a number of areas in the API that will be getting future attention as demand for our API grows in popularity.
    0
    Comment actions Permalink

Please sign in to leave a comment.