Drive Explorer SSO Enablement Using IBMid

Current Issue

Drive Explorer currently relies on a generic account with a shared static password to perform file transfers between environments. As multiple team members use the same credentials, it is difficult to determine who initiated or completed a specific file transfer activity. This lack of individual user identification reduces accountability and makes activity tracking and auditing more challenging.

Problem Statement

The use of shared generic IDs and static passwords presents both operational and security concerns:

• User actions cannot be accurately attributed to an individual.

• Audit trails lack sufficient detail to identify the actual user performing file transfer activities.

• Shared credentials increase the risk of unauthorized use or misuse.

• The current approach does not align with security best practices for access control and accountability.

• Password sharing creates additional compliance and audit challenges.

Proposed Solution

Implement Single Sign-On (SSO) integration between Drive Explorer and IBMid so that users authenticate using their individual corporate credentials rather than a shared generic account.

With IBMid-based authentication:

• Each user accesses Drive Explorer using their own identity.

• All file transfer activities are logged against the authenticated user.

• Complete traceability and accountability are established for every action performed.

• Shared passwords and generic IDs can be eliminated.

• Security controls and audit compliance are significantly strengthened.