AWS Identity & Access Management vs. Oracle Cloud Infrastructure Identity Access Management (OCI IAM)

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

• DJSIR Oracle Identity Cloud Service is federated with DJSIR SSO. When an employee leaves the company an office account will get deleted but it's not reflecting in Oracle Identity Cloud Service or the profile is not getting deleted from Oracle Identity Cloud Service console.
• Oauth setup for the application is a bit confusing
• Increase the number of reports available

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

The support for Oracle Identity Cloud Service is generally good. Nevertheless, it can take some time to get a response from the support team which creates initial frustration, and the customer will have to wait till the SR gets assigned to a support person.

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

Oracle's Identity Cloud Service works more in conjunction with the aforementioned. I think it works similar to Oracle Identity Management (OID) but seems a little more abstracted.

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

• It streamlined our Oracle PAAS implementation where we were able to achieve single sign-on functionality seamlessly.
• It provided us the feature to restrict outside access.
• It provided us with features to perform social IDP configuration for our custom applications.

Incentivized