Google Cloud Identity vs. Passly by ID Agent

For example, if the system you are building is a general application service that does not primarily focus on ID management, it would be wise to use a service like Google's rather than developing your own IDaaS. While there may be cases where an IDaaS other than Google's is acceptable, Google is likely one of the best solutions when considering user recognition and ease of use. On the other hand, Gmail addresses are commonly used for other purposes, and users may not pay much attention to password management, so you should avoid using them for systems that require security. To strengthen security, you should consider making multi-factor authentication mandatory, etc.

Incentivized

From my experience, Kaseya made a mistake with Passly. It does not work correctly. When it does work it is very delayed causing issues for logging into the system. When Kaseya was contacted they could not find users at all. When they finally found the users they could not edit it needing them to escalate to development to fix accounts.

Incentivized

• Two-factor authentication available.
• The Google authentication method is familiar to many users.
• It is expected that it will also support authentication methods that will become common in the future.

Incentivized

• AuthAnvil is simple to use. Whether using an OTP code or push notifications, the application is user-friendly.
• AuthAnvil applications are easy for the end-user to install.
• AuthAnvil is readily available across multiple platforms (Windows, Android, iOS).

Incentivized

• This time, I investigated it in advance, and it worked as expected, so I don't have any specific ideas for improvement.
• Additionally, if we were using another IDAAS, it would have been beneficial to have knowledge on how to integrate it with Google tools, along with some relevant case studies.

Incentivized

• Web interfaces are relatively complex, not entirely ready for end-users
• Token transfers are slightly cumbersome (e.g. moving from hard to soft-token and vice-versa)
• It remains as a separate, local AD-driven solution, independent from external, rising auth platforms (e.g. Azure)

Incentivized

I chose Google because I thought it would be the best fit, but I didn't fully consider other cloud platforms (Azure, AWS, etc.), so I rated it 8. We assume that current Japanese users are familiar with Google, because we feel that there are far more people with Google email addresses than those with IDs on other cloud services.

Incentivized

Simplicity of use combined with price and low system resources.

Incentivized

They are very helpful with helping us with any issues. There are a lot of helpful guides online if you get lost. Kaseya is also good about not bugging you with notifications. Kaseya offers easy to access to support options. Overall I have not had to contact them over a lot of issues. The software rarely broke or was down for maintenance.

Incentivized

We adopted Google Cloud Identity as an additional feature because it allowed us to integrate with it using multi-factor authentication. The IBM Cloud platform remains valid, and we have no plans to discontinue its use for identity management. From the user's perspective, we simply added more authentication options. This also ensures we are prepared for future use when multi-factor authentication becomes available for user apps on the IBM Cloud.

Incentivized

We have transitioned our Multi-Factor authentication processes to use either Authy, Duo, or Microsoft Authenticator, depending on the application use-case. We still have some clients using AuthAnvil, but it is no longer our preferred application for MFA. The other offerings in the market fulfill the same requirement with either lower or no additional cost and are easier to manage and more consistent in their performance.

Incentivized

• From a business perspective, there were two steps.
• First, we switched from our in-house ID management system to a cloud service. This allowed us to focus our development resources on application development.
• At the same time, we were able to localize the handling of personal information, which resulted in increased efficiency in management aspects, including handling external inquiries, and in the development of encryption.
• The second step was adding Google Cloud Identity as an option.
• This allows more users to easily use our services. It can be said that this has improved user convenience.
• I expect Google to accommodate future changes in authentication requirements, such as biometric authentication.

Incentivized

• Using AuthAnvil to log into Kaseya VSA multiple times was definitely a loss in productivity.
• AuthAnvil did provide lots of security for our products because everyone would be deterred by AuthAnvil and Kaseya VSA's labyrinth-like log in process.

Incentivized