torben

Hi,

at the moment I'm testing Workspace on my Android mobile.

Here I am encountering some timing-problems:

• it takes very long to process the login

• login-credentials are lost after short periods (sometimes minutes)

• after selecting a password, it takes about > 10s untill it is shown

What I tested so far (same behaviour)

• Personal Hub

• Devolutions Server (on Premises)

Using same device with browser is really quick, so seems not to be some network-problem.

May be you have a hint for me?

Best regards,

Torben

Sorry for intruding in this thread, but is this also the reason why I can't get the OTP key to update on a username/password credential with Set-RDMEntryOTP? It appears to only work on OTP entries.

@JelmerJ

Hi Jelmer,

have you tried Christians answer from the beginning? This way you should be able to set a credentials TOTP.

Best regards,

Torben

Hello,

Thank you for reaching out on this matter.

I was able to reproduce the issue you are experiencing with the certificate export. I will report this bug to the development team, and they will begin working on a fix soon.

I will follow up with you as soon as a fix is deployed in a future update.

Best regards,

@Jacob Lafrenière

Hi Jacob,

have a similar problem with PDF. Create a new entry in RDM - all fine.

Export as .rdm and re-import at DVLS - attachment "visible" in list but broken.

Best regards,

Torben

Hello Torben,

There's currently no way to set a website entry's OTP key from the DS cmdlets.

However, within the RDM cmdlets, Set-RDMEntryOTP will receive an update in the next major release permitting this.

Best regards,

Christian

@Christian Robert

Hello Christian,

if there would be a way just to crypt the key to the correct value for OTP (Webbrowser seems to crypt different from credential), I'll do the rest.

Best regards,

Torben

Hello Torben,

Here are a few examples of how to modify an existing entry's custom field values.

To modify a custom field which has already been set on the entry:

$credEntry = Get-DSEntry -VaultID $vaultId -FilterMatch ExactExpression -FilterValue $entryName;

$credObject = $credEntry.data | Convert-XMLToPSCustomObject;

$credObject.Connection.MetaInformation.CustomField1Title = "UpdatedTitle";

$credObject.Connection.MetaInformation.CustomField1Value = "UpdatedValue";

$newCredXml = $credObject | Convert-PSCustomObjectToXML;

$credEntry.Data = $newCredXml.OuterXml;

Update-DSEntryBase -FromRDMConnection $credEntry;

If a custom field hasn't been set, the related attributes likely won't show up in the MetaInformation object. In that case, you'll need to add them manually:

Add-Member -InputObject $credObject.Connection.MetaInformation -MemberType NoteProperty -Name "CustomField1Title" -Value "FirstFieldTitle";

Add-Member -InputObject $credObject.Connection.MetaInformation -MemberType NoteProperty -Name "CustomField1Value" -Value "FirstFieldContent";

To modify a custom field's value if it's set as sensitive, you'll need to encrypt it. Here's how:

$credObject.Connection.MetaInformation.SafeCustomField1ValueSensitive = [Devolutions.RemoteDesktopManager.Business.ConnectionMetaInformation]::FilterCustomFieldValueSensitive("NewSensitiveData");

To switch a field from plain-text to sensitive:

$credObject.Connection.MetaInformation = $credObject.Connection.MetaInformation | Select-Object * -ExcludeProperty CustomField1Value;

Add-Member -InputObject $credObject.Connection.MetaInformation -MemberType NoteProperty -Name "CustomField1Hidden" -Value "true";

$sensitiveData = [Devolutions.RemoteDesktopManager.Business.ConnectionMetaInformation]::FilterCustomFieldValueSensitive("NewSensitiveData");

Add-Member -InputObject $credObject.Connection.MetaInformation -MemberType NoteProperty -Name "SafeCustomField1ValueSensitive" -Value $sensitiveData;

One last note: the MetaInformation field should show up if the entry has a password history (ie. if its password has been set at any point in the past) or existing custom fields. If neither of these are present, the MetaInformation might not appear. In this case, you can just do the following to create it:

Add-Member -InputObject $credObject.Connection -MemberType NoteProperty -Name "MetaInformation" -Value ([PSCustomObject]@{})

Best regards,

Christian

@Christian Robert

Dear Christian,

yes - that did it 😃

Thank you very much.

I would appreciate to have such information in Examples on GitHub, also the ones concerning the usage and availability of the pure Devolutions.Powershell-Functions .

Best regards,

Torben

Hello,

Thank you for reaching out regarding this matter.

If I understand correctly, you’re looking to import both shared and personal KeePass data into the Shared and Employees User Vaults without losing any fields.

If that's the case, it should be possible to achieve this using a custom PowerShell script.

However, if I’ve misunderstood your request, please let me know which part I got wrong so we can clarify and find the best solution together.

Best regards,

@Tommy Sanders

Hello Tommy,

as Min said it is not possibile to reach a users personal vault by powershell.

Do you have any other information or hint?

Best regards,

Torben

Hi Min,

one last question I haven't found concerning exporting.

What options would our administrators and users have to get the contents from all stored vaults (personal and shared)

including all the information (Credentials, OTPs, URLs, Custom-Values, Documents/Attachments) including the structure (folder)-information.

I think about what would happen, if for any case, all the included data needs to be exported for further usage.

This means, that all the information requires to be unencrypted or encrypted in a way it's decryptable by admins/users independant from DVLS.

Please consider that about >230 of the pure users would not have a RDM-License to access their personal vault.

Best regards,

Torben

Hello Min,

thanks for your explanation - too bad. XML or JSON would offer great possibilities to allow an universal structured import to Devolutions, with a very low hurdle for unexperienced people at the using end. Maybe this could be a feature-ticket for your developers.

However - I'll concentrate on building this by C# with integrated PowerShell and introduce this to my colleagues.

Best regards,

Torben