We're customers of OneIdentity's from version 7.x. We're on 8.1.3 now and feel like on a crossroad.
At that time, 2017-2018 , we used Oracle as our product backend database. In 8x that was changed to Mysql. We had to purchase extra licenses , servers , support and training on Mysql. And finally get the most customized utility ever to convert the whole schema to the new database. Fortunatelty it worked. It wasnt a complex schema though.
We're still using Oracle as a connected system. Up to 8.2 we used Devart as part of the ADO.Net system connection to Oracle and within our script libraries. In 8.2 this has been replaced by ODP.Net. So , again, we've changed all the references in our code to ODP. And it works. Great. But once again...
In <= 8.1.3 OneIdentity published the DSI connector and encouraged customers to use it as a single point connection to db systems, included Oracle. Turns out it does not work with Oracle. We've created a SR and waited a month only to know that we still need to stick to ODP no matter what. But what will be the future of ODP? or DSI? Are we safe with whichever our option?
In 8.1x OneIdentity announced they were moving the web interface from the current designer to html5 with Angular. As part of our license and support renewal process we purchased training , a whole course, on the current web designer. Turns out this is on a deadline and now we feel we're dumping our money. Once again...
Our local partner has also told us that eventually VB will be replaced by CSharp. Another code retouching...
Now OneIdentity releases a new LTS contract that guarantees support no-matter-what. Is this they're finally getting aware of the pain they're causing to their customers? But again, the solution implies more money.
As a tech guy that works with the product sometimes I feel I'm spending more time dealing with these changes than working with the product itself. Am I alone?
I will be in Barcelona later this year and I would like to see this on the table.