search

pspete / PoShPACLI

Powershell Module for CyberArk PACLI
MIT License
72 stars 20 forks source link

Get-PVUserList returns data in the wrong attributes #54

Closed jsuchovsky closed 6 years ago

jsuchovsky commented 6 years ago

Your issue may already be reported. Please search existing issues before creating one.

Your Environment

Expected Behaviour

When running $Test = Get-PVUserList -Vault $Vault -User $PACLIUser, it should return user data with each object in the array being a different user.

Current Behaviour

When running the command, $Test = Get-PVUserList -Vault $Vault -User $PACLIUser, it returns data in the wrong columns, with more than one user being in one object of the array.

Username Location Disabled LDAPUser GWAccount UsedQuota

Master \ NO NO NO 0 -1 USER NO NO \System 71904 2 NO USER \ NO 0 YES 3 NO Batch USER 1 NO NO -1 5 DR NO NO NO 0 1 -1 NO NO GROUP \ Auditors 0 NO NO 8 -1 \System GROUP NO 1 0 9 GROUP Vault Admins NO \System 1 11 -1 NO NO Notification... 0 0 NO NO -1 PasswordManager \ NO NO NO 0 -1 USER NO NO \ 0 16 NO USER \ NO 0 NO 17 NO PVWAGWAccounts GROUP 0 NO

Possible Solution

Steps to Reproduce (for bug reports)

1 . Log in using, Connect-PVVault -Vault $Vault -User $PACLIUser -LogonFile $Credfile

2 . Run, Get-PVUserList -Vault $Vault -User $PACLIUser

3 .

4 .

Sample Output

Username Location Disabled LDAPUser GWAccount UsedQuota

Master \ NO NO NO 0 -1 USER NO NO \System 71904 2 NO USER \ NO 0 YES 3 NO Batch USER 1 NO NO -1 5 DR NO NO NO 0 1 -1 NO NO GROUP \ Auditors 0 NO NO 8 -1 \System GROUP NO 1 0 9 GROUP Vault Admins NO \System 1 11 -1 NO NO Notification... 0 0 NO NO -1 PasswordManager \ NO NO NO 0 -1 USER NO NO \ 0 16 NO USER \ NO 0 NO 17 NO PVWAGWAccounts GROUP 0 NO

Context

Was trying to use it to see if users already have an account in CyberArk.

pspete commented 6 years ago

Hi @jsuchovsky. Yes, different versions of PACLI do not produce the same output. PACLI 7.2 was used for development of this module, I do not have version 4.1 available to me to replicate the issue you describe.

I think @kruhmann has resolved this in their fork at this link

jsuchovsky commented 6 years ago

Pete,

Thanks, I updated to 9.7 and the issue went away.

Josh

On Fri, Feb 23, 2018 at 4:28 AM, Pete Maan notifications@github.com wrote:

Hi @jsuchovsky https://github.com/jsuchovsky. Yes, different versions of PACLI do not produce the same output. PACLI 7.2 was used for development of this module, I do not have version 4.1 available to me to replicate the issue you describe.

I think @kruhmann https://github.com/kruhmann has resolved this in their fork at this link https://github.com/kruhmann/PoShPACLI/commit/479a9ac28f794a76466fd891d8680f7a5786fbc5#diff-7c4f325cfb84e5c3636e6dab98d07b74

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pspete/PoShPACLI/issues/54#issuecomment-367956255, or mute the thread https://github.com/notifications/unsubscribe-auth/AjC0MTMikyiPtE5Y-RoyOVFYVEEW9QSfks5tXoTCgaJpZM4SQApB .

pspete commented 6 years ago

Glad it is sorted