Google Cloud Identity vs. OneLogin by One Identity

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

OneLogin is very convenient. Users can register their own iPhone or Android to act as their authorization device, meaning they will likely always have access to the OneLogin security code. The OneLogin application then allows the users to hit a button instead of inputting the security code to validate their two-factor authorization. OneLogin is great for businesses who need to enforce secure access into their various systems and tools. By consolidating the security into a single login with security device two-factor authorization, it makes it safe and easy to manage.

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

• Connects with a lot of different vendors, tools, and sites. It is also customizable to where you can add almost any site you are logging into. This makes it especially useful for team members who may use a tool that other team members within the company do not use.
• It works. I've used a few keychain apps that work for a little while, or never work, and this app works 99.99% of the time. Only on one experience have I experienced issue access sites and that was due to user error.
• It's easy to update passwords and usernames within the app. It allows password resets to be an easy process and lowers the time in updating items everywhere.

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

• Lack of administrative APIs for creating or setting up new connectors: This prevents the automated integration to federations and requires manual setup rather than discovery-based automated setup.
• Customization of the interface: The potential configuration of the interface are still limited at the moment (logo, primary and secondary colors, background). This prevents the usage of the platform as a communication medium or to organize the space in a more standard fashion (for our institution)
• There are some limitations with using the apps provisioning APIs that can lead to some termination or provisioning actions not being completed

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

OneLogin is very easy to use. The most complicated part is the user setup and even that is not difficult. After everything is working, using it day to day is trivial. All you have to do is have the application ready on your phone and you can use a single set of login credentials to access all of your tools securely.

Incentivized

There has never been an issue where I have needed to use the OneLogin support so it would be unfair to rate them anything other than a 10 on their ability to provide support. Like I said its a very basic platform that we use it for with no issues.

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

OneLogin has a lesser cost as compared to other solutions. It also has a successful POC, partner expertise, integration with in-house and cloud-based apps, and provides restriction of access from unauthorized devices. It is a secure solution with industry-standard encryption, a good dashboard, and a cloud-based solution. In my opinion, there is not too much effort involved in the integration and it provides good OEM support.

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

• The one big benefit would be time-saving. It is a very convenient platform.
• The access outside of the office also allows me to work at home or in my spare time for additional business that needs to be taken care of.

Incentivized