Add OCI Object Storage provider with multi-auth support (Instance Principal, Workload Identity, Resource Principal, OCI Profile, Session Token)

[sanjeev260191]

Describe the feature or potential improvement

Summary

Add native Oracle Cloud Infrastructure (OCI) Object Storage as a StorageService provider in Langfuse, alongside existing providers such as S3, GCP, and Azure.

The integration should support multiple OCI-native authentication strategies:

• Instance Principal
• Workload Identity (OKE)
• Resource Principal
• OCI Profile (~/.oci/config)
• Session Token authentication

Motivation

Organizations running Langfuse on OCI infrastructure (VMs, OKE, Functions) need a secure, cloud-native storage option without relying on S3-compatible endpoints.

OCI-native support allows:

• Secure IAM-based authentication without long-lived keys
• Better integration with OCI tenancy and policies
• Compliance alignment for OCI-only environments

Proposed Implementation

• Implement a new StorageService adapter using the OCI native SDK via LANGFUSE_USE_OCI_NATIVE_OBJECT_STORAGE.
• Add an authentication factory to dynamically select auth strategy via LANGFUSE_OCI_AUTH_TYPE.
• Ensure full compatibility with existing StorageService interface.
• Support upload, download, list, and delete operations.
• Add unit tests and gated integration tests.
• Update Dockerfile and package.json to include OCI SDK dependencies.
• Provide .env.dev-oci.example with usage instructions.
• Ensure no breaking changes to existing storage providers.

Additional information

Environment Variables

Example configuration:

LANGFUSE_USE_OCI_NATIVE_OBJECT_STORAGE=true
OCI_AUTH_TYPE=workload_identity | instance_principal | resource_principal | oci_profile | session_token

Testing Plan

• Add integration test example that runs only when OCI env vars are present.

Acceptance Criteria

• OCI storage adapter implements StorageService interface
• All auth types supported and validated
• Tests pass locally and in CI
• Docker and env documentation updated with sample .env file
• No breaking changes introduced

I will open a PR implementing this feature once maintainers confirm alignment on the approach.

[Steffen911]

Hey @sanjeev260191 ,
Thank you for the suggestion. We'd be happy to accept community contributions around this.

[sanjeev260191]

@Steffen911 Thanks. I’ve opened a PR, it's currently pending a few checks. Would you be able to take a look or help expedite the review/merge process?
Link to the PR: #12379

[sanjeev260191]

@Steffen911 I have updated rthe PR and need approval to run the checks, would you be able provide approval so that the tests run?

[Steffen911]

@sanjeev260191 Running!

[sanjeev260191]

@Steffen911 Need your approval to run the tests, Please provide when possible

[Steffen911]

@sanjeev260191 Thank you a lot for the contribution!

[jannikmaierhoefer]

Looping in @langfuse-pylon