AWS Identity & Access Management vs. OCI Identity and Access Management

AWS Identity & Access Management is well suited to managing AWS application access between services. Very helpful for both third-party products and in-house developed software. Very happy with how easy it is to create access keys and then share them in our environment. AWS IAM can also be used to manage individual users, but I highly recommend using AWS SSO for that purpose instead. Much easier to deploy for console access and from a security side easier to turn off in one click from your SSO provider.

Incentivized

Scenarios where IDCS is well suited:

• Oracle Identity Cloud Service is well-suited for organizations that require a centralized approach to managing user access and authentication across multiple applications and services.

• Organizations with strict compliance requirements

Scenarios where IDCS might be less appropriate:

• Organizations with limited customization requirements

Incentivized

• Customized access per key to limit scope
• Safely distributes access keys
• Provides access audits

Incentivized

• Restrict access to the applications outside our organization network.
• Multiple IDP configurations make it easy for us to authorize access.
• The adaptive security feature lets us know high-risk users.

Incentivized

• Better integration with roles and policies so you don't need three windows open to create a new IAM user
• Display recommended configurations based on services being used
• Easier options to base config on existing users

Incentivized

• The web interface has gotten better over the years, but some functionality is still being handled via shell commands.
• SSL setup can be simplified into one place instead of having to navigate to multiple pages and update different key-stores or wallets.
• Migrating and or replicating between versions can be more intuitive with a side-by-side comparison of schema/attributes.

Incentivized

We would be unable to manage the interconnected nature of our AWS services without AWS IAM.

Incentivized

Oracle cloud services meets most of our needs. I hope in the future we could look at more of the OIG functions included so we could move away from needing to stand up that component.

Incentivized

We have contacted Oracle support a few times regarding admin access queries and every time we received prompt replies and help. In my experience, we only contacted 2 times in 3 years. I think it's because of ease of use and manageability. Also, Oracle Identity Cloud Service customer care team was pretty fast and helpful.

Incentivized

While we do not use Microsoft Azure for our servers and other customer-facing services. If we did, we would have to use Microsoft Azure Active Directory to manage access to services appropriately. It's difficult to quantify the differences between the services as they are truly different. I would recommend choosing AWS or Azure, then using the identity management provided by the same vendor.

Incentivized

I believe we had a quite fair RFP listing all our complex integration and being key on utilizing existing investments, the Oracle product met our requirements and the local partner presented that very well. With such combined synergy, the offering was appealing to be the winning bid and therefore Oracle Identity Management was selected.

Incentivized

I hope at some point we could get away from needing to "bring our own" licenses and just have a unique user login rate.

Incentivized

Oracle provided various services we could take advantage of to get the environment configured correctly without needing to hire contractors.

Incentivized

• Without IAM, it would be difficult to use AWS across services. Increased ROI

Incentivized

• I'm not sure we've seen actual ROI by implementing this product. We had many efforts to look at alternatives and to evaluate newer versions (OIG). In the end, we decided to replace it with Sailpoint.

Incentivized