Success Stories

Radiant Logic Customer Success Stories

Read more about how RadiantOne enabled our customers to solve challenging integration problems and leverage existing infrastructure investments with virtualization solutions.

Customer Testimonials: Nick Bishop

The RadiantOne federated identity and directory solutions have vastly improved the way many large enterprises and Fortune 1000 companies have done business. Included here are rave reviews from Symantec, the Federal Reserve Bank, Booz Allen Hamilton and NYISO. Hear the real-world success stories of Radiant Logic in action.

Case Study: Beverage Corporation

Read the story → RadiantOne simplifies the identity infrastructure of a multinational beverage corporation by integrating all the identity data from across a diverse array of identity data stores into a virtualized identity hub.

The corporation’s identity infrastructure had become complicated and expensive to maintain. It was time to simplify. The challenges they faced in this effort were:

  • Authentication had slowed down over the years as the corporation had added user populations and the current infrastructure could not satisfy the growing demand for finer-grained authorization.
  • It had become difficult to add new identity sources—often requiring custom hard-coded connections.
  • Searching through an identity infrastructure that included multiple data sources was time consuming, slowing logins and frustrating users.
  • There was a risk the same username was in more than one Active Directory and users could get locked out because the wrong password was presented.

Case Study: Consumer Goods Manufacturer

Read the story → Modernizing Infrastructure to Prepare for a “Cloud-First” Future

The Challenge:

  • The company was saddled with an elderly metadirectory that was costing increasing amounts every year to run, while no longer being supported or updated by Critical Path. This metadirectory was also supplemented by a variety of different directories and databases, including a multi-domain AD infrastructure.
  • This complex and aging infrastructure made it much more difficult to move to the federation and the cloud or enable other initiatives such as acquisitions and divestitures.
  • Because this aging metadirectory was not SHA2-certified, the company was out of compliance with current standards.
  • The company spends $2 billion per year outsourcing its IT function and that vendor predicted a large rise in costs for its team to continue supporting Critical Path.
  • The company wanted to stop the increasing payments on its Critical Path infrastructure and also make it easier to enable its Sailpoint and Siteminder investments, as well as a future Ping deployment.

Case Study: Energy Industry

Read the story → The M&A Identity Integration Initiative

The Challenge:

  • Identity data was spread across many disparate identity data sources. To provide access to users from each of the companies in the merged entity, this data needed to be fully integrated, both to streamline the authentication processes and to protect security.
  • The schedule was compressed to meet the timelines of the merger.
  • A lot of concurrent activity caused contention for resources, since many people were on more than one corporate integration initiatives.

Case Study: Entertainment Corporation

Read the story → The “One Identity” Initiative

The Challenge:

  • The company wanted users from their many subsidiaries to have access to common corporate applications with single sign-on.
  • Each subsidiary had its own identity data store and they weren’t all the same.
  • Their identity infrastructure contained multiple AD domains and forests, in addition to LDAP directories, making it a challenge to find and authenticate users.
  • They wanted to provide single sign-on, but did not want to disrupt the existing identity infrastructure.

Case Study: Financial Institution

Read the story → Migrating Away from Aging Sun Directories

The Challenge:

  • With a complex infrastructure, including multiple AD domains and forests and several separate LDAP directories, this bank had to custom code each new connection, creating a brittle patchwork of links that wasn’t flexible or easy to update. Managing all these user stores was an expensive administrative burden.
  • Although each new application was costly and time-consuming to integrate, single applications were not viewed as enough to warrant a new strategy, but when the aging Sun LDAP system reached its end-of-life, the identity team finally had a reason to make the move to a more modern directory infrastructure with federating identity capabilities based on advanced virtualization.

Case Study: Financial Services

Read the story → RadiantOne adds flexibility and versatility to the identity infrastructure of a global financial services company, facilitating updates to identity information of its 200,000 employees.

The Challenge:

  • Difficult administration of user status changes in AD and LDAP
  • 860,000 updates/minute from changes in status, certification, groups, and names
  • 200,000 employees; 600,000 identities
  • 24 Active Directory domains
  • 16 LDAP directories
  • 6-Month Managers Certification Program

Case Study: Food Industry

Read the story → Providing Secure Access to Corporate Applications and Single Sign-On For All

The Challenge:

  • Because their infrastructure contained a diverse array of identity data sources, it had become expensive to maintain, and providing single sign-on and secure access to corporate applications for franchises was an expensive and labor-intensive proposition.
  • Integrating new applications with a single sign-on solution quickly and cost-effectively was a significant challenge.
  • The corporation wanted to centralize and normalize data in their MDM solution, but faced performance and high availability challenges.

Case Study: Healthcare Industry

Read the story → Day One Readiness: Using RadiantOne FID to Prepare for M&A

The Challenge:

  • The acquisition of another large healthcare organization created a road block to securely accessing each other’s applications and working together effectively.
  • The goal was to combine organizations without having to establish trust or share administration between each AD environment; this meant the company needed a way to logically centralize identity, while still respecting existing identity stores and investments.

Case Study: Healthcare Industry

Read the story → RadiantOne helps healthcare giant simplify logins, dramatically improving users’ single sign-on experience.

The Challenge:

  • Doctors, nurses, care providers, other employees, and partners had too many user names and passwords and it was impeding care. They decided to start an initiative to simplify the infrastructure called “One User, One Identity, One Password.”
  • They tried to achieve their goal with one well-known vendor and then with another, but were unhappy with the results each time. Although executives historically had preferred stack vendors, after years of searching for the right solution, they finally decided to explore best of breed offerings.
  • The status quo became even more complicated when the previous vendor deprecated the product the consortium had deployed and were pushing a newer product which lacked functionality they had originally offered.

Case Study: Healthcare Industry

Read the story → Creating a Foundational Identity Service for M&A and Critical Healthcare Applications with RadiantOne

The Challenge:

  • Along with other initiatives, the company wanted to move from using 3 EMRs/2 vendors to Epic by 2019.
  • The company’s external identity management environment supported approximately 25,000 logins per day for more than 25 applications.
  • There currently is a user base of approximately 550,000 logins with a growth rate of more than 10,000 users per month.
  • Future growth rates are expected to increase with additional applications.

Case Study: Healthcare Industry

Read the story → Groups Management and Virtualization

With RadiantOne FID, a large integrated managed care organization created one global view of all their user accounts by aggregating identity information in their LDAP and AD domains to build a global profile of each user or customer. However existing groups needed to be translated/mapped into the new “naming/addressing scheme” to take full advantage of the global view created by virtualization. RadiantOne tools such as the Groups Migration Wizard allowed the company to migrate groups painlessly and provided an optimized, rational and unified view of group membership.

The Challenge:

  • Most organizations rely on roles/groups-based authorization, but the more the size and number of groups grows, the more difficult managing these groups becomes. Users can be employees, contractors, patients, insurance customers or physicians, to name a few, and they’re often engaged in many different activities across many cost centers. With frequent user overlap across groups and no easy way to gain a global view across all groups, managing these groups manually had become an expensive, time-consuming hassle with the potential for dire consequences.
  • In consolidating identity stores, and unifying them through virtualization, the company faced the challenge of group migration. Without the support of advanced tools, building and managing groups for access management can be a never-ending process that often calls for compromises in either security or agility.

Case Study: Healthcare Industry

Read the story → Support for M&A and Seamless, Logical AD Consolidation in a Healthcare Setting

RadiantOne helps a large healthcare organization streamline its identity infrastructure and provide one global, rationalized list of all its users, improving user experience, boosting the security of the system and paving the way for integrating new user identity data in future mergers and acquisitions.

The Challenge:

As the company brought in new organizations, it needed to secure access for new employees to existing LDAP applications. It also wanted to roll out Kronos, but had no single logical storage where all user information could be found (in the format required by Kronos).

  • The company had eight Active Directory domains and many tightly coupled AD applications.
  • All new identities from the merger must be granted access to the enterprise employee time management application (Kronos) along with other important corporate applications.
  • The company had a set of LDAP applications that were provided SSO through RSA Access Manager and they wanted to extend access to the new users from the merger.
  • These applications need one source of definitive identity information on users—both existing and new users—for authentication and authorization.

Case Study: Insurance Industry

Read the story → A 360-Degree View of Customers Across Multiple Business Service Areas

The Challenge:

  • Historically, customers registered for services through different platforms, each with its own user store, which meant
    customers had to login multiple times to access services, while remembering multiples usernames and passwords—and these challenges existed across all user types, including individuals, intermediaries, and institutional users.
  • Because Self-Service/Password Reset (SSPR) functions were performed from within the BU applications, there was no central place to make changes—making an already difficult user experience even more cumbersome.
  • The company needed a way that would eventually enable customers to “log in once and log in everywhere,” while also allowing each business unit to shift to the new system on its own schedule.

Case Study: Insurance Industry

Read the story → Transforming the Digital Experience for Customers

Global Insurance Group Makes Logins Easier Across Hundreds of Sites

The Challenge:

  • A global company that had added product lines through acquisition was having trouble with a cumbersome authentication process that spanned many different applications.
  • Users were having to remember multiple logins and passwords for each separate site—not a great experience for internal audiences, and an extremely bad experience for customers.
  • Each site maintained local control over authentication, but the company needed a way to centralize the security experience while maintaining each site’s autonomy.

Case Study: Insurance Industry

Read the story → Creating Best-In-Class Customer Experience

A large insurance company chooses RadiantOne Federated Identity and Directory Service to improve its customer experience with faster, smarter authentication and authorization.

The Challenge:

  • Large number of users
  • Diverse user population composed of agents, contractors, and customers
  • Each product had its own web site and directory for authentication and authorization
  • Duplicate identities across different backends
  • Customers had to deal with multiple usernames and passwords

Case Study: Retail Chain

Read the story → Moving from Static to Dynamic Groups

The Challenge:

  • The identity team needed a way need to dynamically manage more than 3000 groups—without having to use a difficult-to manage homegrown system.
  • Having CA write code to make those groups easier to manage cost more than the company was willing to spend.
  • The new CIO inherited this problem and was looking for new ways to solve these issues, without having to spend as much time or money.
  • The most complex and time-consuming issue with groups was having to make changes manually.

Case Study: Telecommunications Company

Read the story → Adding Acquisitions Quickly: Providing Immediate Access with RadiantOne

The Challenge:

  • This major cable and communications giant purchased two sizable competitors and needed to integrate both acquisitions into the existing network in a very timely fashion.
  • The company needed to protect directories by abstracting them from developers, as well as outside forces.
  • For billing and customer satisfaction purposes, the identity team needed to roll out a “day one” solution that worked seamlessly for both internal and external identities.
  • Any other option would have involved many months or years of sunk costs and brittle custom coding.