motz

People need to remove ALL previous modules and versions - if they want to avoid hitting the same issues I have been facing. Got some strange errors about types and stuff, that couldn't be casted.

But unregister the old vault, remove the legacy modules and making sure that I only had 2023.1.0.8 installed - start a new PowerShell session, worked flawlessly

Just did my initial test - and it works.

Thank you for the very fast response to my issues!

I said that a bit to early:

In the legacy module I can retrieve the secret, like this:

$tmp = Get-Secret -Name [SecretName]

$tmp.GetNetworkCredential().Password

But in the new module, the secret is blank, doing the same thing. I got a feeling that you don't populate the credential object with all properties.

So for now I need the legacy module, to obtain my secret value and the new module to obtain my metadata.

Should I start a new thread for us to collaborate on the missing secret information in the new module?

Just a quick update:

I now have all the features that I expect from SecretManagement. The meta data capabilities just works, which is going to make my life easier!

Thank you very much 😁

That worked flawlessly!

I can adjust my scripts to work with this 🤘

I tried the following:

Install-Module -Name Devolutions.PowerShell

$parms = @{}

$parms.VaultId = 'GUID'

$parms.ApplicationKey = 'AppKey'

$parms.ApplicationSecret = 'AppSecret'

$parms.Url = 'https://COMPANY.devolutions.app'

Register-SecretVault -Name "TEST" -ModuleName Devolutions.PowerShell -VaultParameters $parms

Test-SecretVault -Name "TEST"

And it didn't fail. I can get secretinfo - but only from the default vault and not my "private" vault that I created, when I created with the first one. I'm splitting my vaults for usage with RDM and PowerShell only scripts. Is it possible to map directly to a specific vault, like with the "legacy" module?

We have several Shared Vaults, and I have a personal Vault. What I'm trying to support is to have a Shared Vault, used for PowerShell scripts / automation, kept clean from all the other objects, in the beginning only for me - but later to be shared across the team, so we can have the scripts working across machines.

Could you share what I need to run, to register a vault via the new module?

Current details, that I'm using with the "legacy" module:

Install-Module -Name SecretManagement.DevolutionsHub

$parms = @{}

$parms.VaultId = 'GUID'

$parms.ApplicationKey = 'AppKey'

$parms.ApplicationSecret = 'AppSecret'

$parms.Url = 'https://COMPANY.devolutions.app'

Register-SecretVault -Name "TEST" -ModuleName SecretManagement.DevolutionsHub -VaultParameters $parms

Test-SecretVault -Name "TEST"

But listing the secrets, shows only one.

I can add multiple entries, with the same logical name.

This leaves me with multiple entries, where I would like to have an error - that I already have an entry with the same name. If I want to overwrite the secret, I would expect to use the -Force option.

For now, the module fetches the first entry, based on the guid id of the different entries. So not even last in or first created. Please take that into consideration.

Hello Motz,

Adding multiple entries with the same name will be prevented.

The default behavior of Set-Secret is to overwrite the existing secret. To prevent this, the switch -NoClobber must be used. No Force switch will be implemented.

Get-SecretInfo will return unique names (group\name). However, it is possible to have two entries with the same name in the same group in Hub. In those case, we are considering returning the ID as the secret name. Get-Secret, Remove-Secret and Set-Secret will fail in those case.

I might be doing things wrong, but with the current modules installed and configured, I get new entries for each Set-Secret. Are you talking about in the next release?

The powershell concept is that you can add a HashTable, that would be appended directly to your secret entry. This would enable the end-user to add any semi-complex metadata structure. This can be all kind of things - so I wouldn't limit what types / structures you should. Honoring the HashTable would make people capable of handle any future scenario, and make it easier to migrate from other platforms.

I can add multiple entries, with the same logical name.

This leaves me with multiple entries, where I would like to have an error - that I already have an entry with the same name. If I want to overwrite the secret, I would expect to use the -Force option.

For now, the module fetches the first entry, based on the guid id of the different entries. So not even last in or first created. Please take that into consideration.

While you're at it, it would make a huge difference - if you could support the metadata concept from the secret management module. It is not supported at the moment.

I've start using the "SecretManagement.DevolutionsHub" powershell module, to utilize that I can store my secrets inside a vault, and fetch them at runtime.

I'm looking for a way, to silence the Progress Bar that is shown while fetching a secret - as I don't need the information:

See below example:

All known PowerShell tricks that would normally hide this, doesn't work.

$ProgressPreference = "SilentlyContinue"

$Global:ProgressPreference = "SilentlyContinue"

If the code is open source, I'm more than happy to assist if possible - to find a way to enabled people like myself to hide this progress.

Clearing the .lyt files first didn't do anything.

Resetting the navigation didn't do anything.

But removing the .lyt files AFTER resetting the navigation worked....

Hi!

I'm seeing a red cross in my navigation list, sometimes when I'm trying to see my favorites and sometimes the entire vault.

If I double click anywhere in the navigation list, it tries to open a connection.

So I believe the list is fully updated and available, but I cannot see it.

I have attached a picture to show how it looks. Has anyone of you ever seen this before?

Hi Jeff,

Thanks for getting back to me 😀

I know about importing rdp files, but I don't see that as an option when I want to have the password imported also.

Reading the link you shared, it states that it can read passwords in using the CSV import. Is that the only import option that can handle passwords while importing the server details? Or could I use the same password tag for the RDM file (XML) and it would work? 🤔

Hi,

First time poster, so please be kind ;)

I would like to know the best way for me to import a RDP connection / RDP details to my Remote Desktop Manager.

I have all the details stored in another platform per company requirements, but I want to be able to export these details in a format, so that I can import a connection into my Remote Desktop Manager without having to type in the password. Is that possible?

Looking at the rdm file structure, I can see that there is a "SafePassord" tag. I expect this to encrypted in some fashion and with at key that you can't share with the public.

I don't have any other devolutions products but Remote Desktop Manager, so I need to understand if it is possible for me to import rdp connection file containing the password. I could live with the option that I import the username and password first from a file, giving them a unique name in the file and reference that name in the rdp details file - but that would be my second choice if I had to pick.

I hope someone can share some details with to understand what is possible and what is not.