Google Cloud Identity vs. Oracle Identity Governance

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

Well suited for: 1. Large and medium organisations who have the capacity to invest in IAM roadmap for long term. 2. Organisations with and existing oracle and partner applications ecosystem. 3. Scenario where the user base is on the higher side and organisations looking to scale up in near future. 4. Organisation with complex workflow need in identity management process. Not well suited for 1. Small organisations or even medium ones which have a lesser number of applications 2. Scenarios where custom connectors need to be developed but at the same time turnaround should be quick. 3. Scenarios when features you are looking for are missing, getting them added could take a lot of effort. 4. UI is not very user-friendly and needs to be customised. 5. Takes time to stablise post going live

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

• It has a very well-defined and scalable framework (LDAP directory).
• It scales particularly well, going from a basic platform to a complex one using customisation and extensions.
• It integrates well with other components like SSO and Access Manager to provide comprehensive a one stop identity management solution.

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

• The cost could be lower.
• Support.
• Identity.

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

Overall good product and somewhat reliable when used in a specific manner. However, there are cons like unending bugs and no well-defined upgrade path. The product could have been more flexible and lite in terms of organisational infra needs. OIM is a robust product but other vendors are almost on-par now.

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

I was not involved in the purchasing decision, an enterprise architect who used Gartner as a source was influential

• 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

• It has a great impact from moving us from paper based to full EHR Compliance
• It's easy to check and see how users get and lose access to the systems that are administered through OIM
• It's also helping in tying down Policies and procedures within the Orgainization

Incentivized