search

darrenjrobinson / powershell_module_identitynow

SailPoint IdentityNow PowerShell Module
https://blog.darrenjrobinson.com/sailpoint-identitynow/
MIT License
47 stars 15 forks source link

Using only PAT for authentication raises errors #44

Closed yannick-beot-sp closed 2 years ago

yannick-beot-sp commented 3 years ago

Perhaps, I'm mistakening but PAT should be enough. When I'm configuring only PAT, I get error in Get-IdentityNowAuth.ps1:160 (I have only the error message in French...).

410sean commented 2 years ago

Hi Darren, it looks like you addressed this in 1.1.6. did you have an eta on publishing the new version? thanks!

darrenjrobinson commented 2 years ago

In v1.1.5 using only a PAT works. I did it again this week looking at this issue

Are you seeing something different?

v1.1.6 has been on my mind though as I need to urgently go through all the v2 API calls and update the GET/Search functions for paging at 250 results per call.

410sean commented 2 years ago

I always had fully populated PAT,v2,v3, and admin username/password but when helping get cowrokers setup they would see an error with only providing a PAT and leaving out the admin username and password.

funny i was getting pinged by our customer success manager to update our calls to cap at 250 so was just looking at that this morning. made some good progress on converting fim criteria groups to roles in identitynow unless they contain calculated members like when sets are included.

Another thing I am also taking a look at is Microsoft's module autorest to convert an openapi documentation file to a powershell module but i'm finding the swagger file from sailpoint's v3 and beta api has a lot of errors in it but I have not spent a lot of time on this.

On Thu, May 26, 2022 at 7:17 PM Darren Robinson @.***> wrote:

In v1.1.5 using only a PAT works. I did it again this week looking at this issue https://github.com/darrenjrobinson/powershell_module_identitynow/issues/56#issuecomment-1135305137

Are you seeing something different?

v1.1.6 has been on my mind though as I need to urgently go through all the v2 API calls and update the GET/Search functions for paging at 250 results per call.

— Reply to this email directly, view it on GitHub https://github.com/darrenjrobinson/powershell_module_identitynow/issues/44#issuecomment-1139136464, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHA7OJZLRWUVWZDKIQTXXDVMABCFANCNFSM5BH3NKUQ . You are receiving this because you commented.Message ID: @.*** .com>

-- Sean McGovern

darrenjrobinson commented 2 years ago

Ah yes, I also used the Admin-name & Password with PAT.

Been a while since I looked at Autorest. It was never as straightforward as it should be/was promised.

https://blog.darrenjrobinson.com/using-autorest-for-powershell-to-generate-powershell-modules/

Appreciate the PR's. Will consolidate for v1.1.6.

410sean commented 2 years ago

still poking at autorest, getting it working with IDN is an effort.

my pull request is not comprehensive update to API but everywhere i could find limit i lowered to 250. my update today on Get-IdentityNowAccessProfile within my fork i'm thinking can be one option for how this module offers api choice and looping using -all switch.