Missing HostAddress in Api response

Missing HostAddress in Api response

avatar

Hi,

what do I have to do get the host information within the api response from the devolutions server? Username, password and name are there but the addresses are missing.

Kind Regards

All Comments (6)

avatar

It's in the undocumented(?) API endpoint

Get all partial connections (connection tree) here: /api/connections/partial/tree/< vault id >

Get the full entry info here: /api/connections/partial/< entry id>

I don't have much more info for you now.

I only started looking into this today, because I want to write some code so I can store entry info in yaml files, in a git repo where we can declare entries as yaml files and (re-) populate the RDM repository instead of letting people make manual changes. End goal being to have some form of middleware so I can also sync with for example ansible/terraform inventory.

There seems to be a lack of information and documentation for this as it's probably expected that click in the interface to make manual changes.
So hoping to see responses to this post with more info regarding the `/api/connections/partial` endpoint

avatar

Hello,

Thank you for your feedback.

The DVLS API supports only username/password credential entries. We recommend using the Devolutions PowerShell module with the Devolutions Server cmdlets as shown in Method 2 of this page. You can find some sample scripts on this GitHub repository.

You can also post a feature request in this section of the forum.

Please let us know if you have any further questions.

Best regards,

Érica Poirier

avatar
It's in the undocumented(?) API endpoint

Get all partial connections (connection tree) here: /api/connections/partial/tree/< vault id >

Get the full entry info here: /api/connections/partial/< entry id>

I don't have much more info for you now.

I only started looking into this today, because I want to write some code so I can store entry info in yaml files, in a git repo where we can declare entries as yaml files and (re-) populate the RDM repository instead of letting people make manual changes. End goal being to have some form of middleware so I can also sync with for example ansible/terraform inventory.

There seems to be a lack of information and documentation for this as it's probably expected that click in the interface to make manual changes.
So hoping to see responses to this post with more info regarding the `/api/connections/partial` endpoint


@rolflobker

Thanks a lot! This makes me so happy. You are my hero of the day!

avatar
Hello,

Thank you for your feedback.

The DVLS API supports only username/password credential entries. We recommend using the Devolutions PowerShell module with the Devolutions Server cmdlets as shown in Method 2 of this page. You can find some sample scripts on this GitHub repository.

You can also post a feature request in this section of the forum.

Please let us know if you have any further questions.

Best regards,


@Erica Poirier
What about documenting what rolflobker said?

avatar

Hello benjaminbendel,

Thank you for this feedback.

rolflobker is right, however, you might run into some unexpected behaviour.
Yes, the entry information will be displayed, but not all of it; some fields will still be empty, including sensitive information.

I suggest that you give it a try and see what could be done in a test vault.
If the API is not doing exactly what's expected, I suggest using the PowerShell module instead.

Let us know if you have any questions or if you want to investigate a specific behaviour.

Best regards,

Patrick Ouimet

avatar

Sensitive information is in:

/api/connections/partial/<session id>/sensitive-data (POST not GET btw)

It's undocumented, thus also unsupported
This means if it breaks , you're on your own

I don't fully agree with " using the PowerShell module "
Some people prefer Python and not having to add Powershell to their Linux systems

While I think it's fantastic that there exist such great Powershell Cmdlets, it does not really fit into my workflow to run Powershell (which also stores session data somewhere -- which needs to be managed). DVLS/RDM such an awesome tool that you might attract other people. People who, for instance like working with declarative code and like writing sysops scripts to manage DVLS/RDM. A powerful and well documented API which does more than just listing vaults is probably going to happen some time :)