Hi Vincent, look at the beginning of the image there is a cat pass.txt. First I copy-paste the examples in documentation, I ended with a simple .txt file with a string “lalala”.
Although capture is from curl, I started in Postman. Moved to curl to see if there was a client problem, but I am still getting the 500 error. Strange that I tried with other tenants and it does not work in anyone. I just created a support case too.
We’re currently working with engineering on this and have identified an issue affecting password dictionary uploads when no existing dictionary is present. While I don’t have a firm ETA yet, we expect a fix to be available shortly.
Thank you for bringing this to our attention - we appreciate the report!
So this would affect customers with a planned go-live deployment that needs a password dictionary. Is there any workaround for the time being? If not, maybe this is a service disruption and should be reflected on https://status.sailpoint.com/?
(Though no one should do a deployment on a Friday…)
Hi @David_Norris - that is correct. This issue only affects customers who have never uploaded a password dictionary before. At this time, there is no workaround; however, our engineering team is actively working to resolve the issue and we hope to have this fixed soon.
I completely understand your viewpoint on the status page. That said, we typically post major incidents - those that cause significant impact across all customers - there, not bug fixes.