AWS Identity & Access Management vs. Jive

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

It's definitely worth considering Jive for the type of application we've developed i.e. a central shared repository for all employees to host and discuss information. I can't say I have ever used a superior tool, but they may exist. I'm just not sure I would want to use it exclusively for file hosting, though. It does integrate with various other tools, so perhaps it would be fine if used in conjunction with another tool for that purpose.

Incentivized

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

Incentivized

• Individual design
• Presence of Russian language (localization can be independently established)
• You can configure several information tapes with different themes. One for work, the second for communication
• A newly-arrived network user immediately receives a prepared block for beginners. After completing several game tasks, the user will receive the basics of using Jive.
• There is a template for each scenario. There is even a template for planning R&D, and there are more than twenty of them.
• Integrates with MS Office, Google Drive, Google Docs
• There are all platforms (even Winphone and blackberry)
• You can create forum threads

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

• Search functionality is very weak
• The information architecture and taxonomy doesnt allow for easy discoverability of content
• It's hard to navigate the and find spaces/groups that I already know about
• The main profile/interface does not allow easy access to key tasks or common tasks.

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

Incentivized

There are always external factors that can impact this decision but currently, the Jive platform is maintaining its lead in the market place in this area. If the innovation in this space by Jive continues, then this number will remain high. Integration with other systems and adaptability to changes in the market or in client needs will also make this decision hard to predict more then 6 months into the future

It was harder to use that expected. The admin needs to be code savvy to truly customize the system. And users need to trained on the system and the setup. Trainings and monitoring need to continue to enforce use.

Uptime was OK. But there was one day that the system crashed for a whole day. Our company was unable to operate. And all the plugins to word/excel froze causing those systems to freeze.

Jive posted a statement to the media saying all customers were up, but we were not.

The product worked as designed. It just didn't work for our needs.

They did an OK job when I needed them. Except for the one day the system went down. Jive pointed the finger at the hosting company, and the hosting company pointed the finger at Jive. No reliable information came to us.

Jive online training is there. It is OK/average. I feel some other companies are doing better. It is not a piece that is required to have a successfully implementation, but it could be useful to improve it

If I did this over, I would hire out the implementation. They know the best practices and could have guided us to make an easier to use setup.

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

We had a Google phone number set up before and Jive was a lot better option than that. It is more consistent and can be configured much easier and with more advanced settings. Additionally, based on the pricing as well as working with the rep on our account, it was a perfect option for us

Incentivized

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

Incentivized

• reduce email traffic
• reduce amount of files/documents scattered & lost across shared drives
• increased discovery, awareness and interaction of historically more separated individuals & team functions across the organisation
• from an IT perspective, we've benefited from improved IT operations (e.g. troubleshooting info shared and easily searched/found with all team members - such that even junior team members can solve technical problems outside of business hours, lessening the burden for standby/call-in for more senior team members)

Incentivized