Please share with the community what you think needs improvement with Tools4ever HelloID.
What are its weaknesses? What would you like to see changed in a future version?
We use HelloID for ourselves and clients, so we need to manage a lot of client environments at once. Functionality to manage this situation is not yet available. When something needs to be changed with the sign-on policies, we have to apply this manually to every client environment that we have.
I would like to have the built-in provisioning module improved. I’ve seen demos in the past of HR systems like AFAS and Raet being connected to HelloID, and perfectly mapped and translated to customizable objects in HelloID. This functionality can be used for numerous solutions. I know that it is on the roadmap, but I would like to see it as soon as possible, in the next release.
In our environment, we use Android tablets. HelloID now supports SSO to web-based applications. Our organization also uses native Android apps, and it would be nice if HelloID could publish these apps in their portal. Integration with other Tools4ever applications such as SSRPM and IAM would be nice.
The things we would like to see in the next release is the ability to provision directly from an HR system, and some more built-in automation calculations, like the calculation for a username. Sometimes it generates a username that is not unique, but at the time of this writing, it is not possible to generate a new one that is unique.
I would like to know the advantages of Imprivata OneSign as compared to NetIQ SecureLogin. What are the advantages of Impravata OneSign in terms of deployment and user experience? Any other advantages?