(user deleted)

Hi,

I've set up the support session.

Thanks!

Thank you sir!

And thanks to the dev team!

Hi,

The logs from servers have been uploaded

I will relay to John, thanks

okay thanks!

The test code I am using is:

EDIT: noticed I had a mistake in my test code and corrected to the above.

Still getting a failure at line 116 of New-DSSession.

Apparently the $NewResponse.isSuccess is still coming back false. We are wondering if something with the Auth works changed in the newer version of the code and the request is getting killed somewhere in our network.

It's got to be something new though because the production code used to work fine before the update and I haven't changed it since I originally got it working

I turned on verbose so we have this error logging in the console:

Logs have been uploaded for the last 7 days per John

will do.

In the meantime I've also had some behavior where I tried to just create a new DS-Session and gotten stuck in some kind of loop where it's trying to open Chrome and opens a bunch of tabs until I CTRL+C on the PowerShell window:

Hi,

We tried a different access key and no luck

They also have all the access allowed

The guy in charge says to tell you that they are behind a WAF and load balancer.

There are two nodes, and a RDS server in AWS

I have not. I will see about getting a new one and then get back to you

Good morning sir,

I convinced them to update our devolutions server to 2022.1.10.0

I also have that version of the Powershell module installed on my computer and I am still getting the Invalid Username and password error out of the DS-Session:

So I'm wondering if it's possible that my secret key is somehow locked or expired in the system. Or if maybe it became invalidated when the system updates were performed?

Any help is appreciated!

That's probably the solution, but I wanted to make sure before I told anyone that.

Thanks!

Hi,

I tried it with both 2021.16.4 and 2022.1.10

Both are giving me the invalid credentials error.

okay will do!

No Dice:

We are using 2022.1.9.999

I'll try that previous version thanks!

Seems like maybe it could be due to our custom version of Password Server being 2022.1.9 based, what is your opinion?

Hi I pasted your commands from above into my test script and changed the appropriate values to be able to access our vault with the result:

okay let me try

Hi I ran the following commands:

Okay it looks like the latest version of the Powershell isn't working. I'm still getting the same error as the person in the other thread:

I may put in a support ticket per our DVLS admin's recommendation

Oops! looks like this is a duplicate of another thread. I am testing the new code now.

Thanks!

Hi all,

Our company uses Devolutions Password Server. Out IT department recently updated from the base October version of DPS to a custom version: 2022.1.9.999

After the update our Secret and key no longer work with the PS module. Instead I just get invalid user errors.

I think it probably has something to do with the update.

Any help would be much appreciated!

Thanks,

Brian Ormond

Hi,

with some error logging I was able to figure out the issue. When I installed the module I didn't do it for all users scope. Once I uninstalled it completely and re-installed for all users things started working.

Thanks!