@raibom ,
One thing worth mentioning - we had ran into an issue with the technical name because of a change SailPoint made recently around how source technical names are generated.
One fine day, SP changed how they calculate the the technical name, it wasn’t just Name [source] anymore. It can now include a longer identifier, something like Name [source-xxxxxx]. Name [source-timestamp]
There was a thread I created about it here, if you want the full context:
Because of that shift, anything that depends on the technical name - like rules, or in your case the query-password-info API - will only work when you use the internal name rather than the display name shown in the UI.
At the time, we thought it was a bug and opened a support ticket, but it turns out this was intentional behavior. They eventually rolled it back for us (and possibly more widely), but it wasn’t clearly communicated.
The main takeaway is: this feature could roll out again without much notice, and if you’re not aware of the change, new deployments or automation could break unexpectedly.
To be fair, the reason behind the change made sense - it allowed creating sources with similar or reused names, since once a source named abcd exists, deleting it normally blocks you from creating another with the same name. The timestamp suffix solved that nicely - we just would’ve appreciated a heads-up before it landed.