CyberSource / CyberSource/cybersource-sdk-dotnet

Certificate *.p12 from configuration file

Open
#44 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
37
Forks
53
PR merge metrics
No merged PRs in 30d

Description

Hi,

I am using service fabric to deploy the application to azure cluster and we do not use configuration but an application manifest generated by service fabric. The RunTransaction() method in SoapClient expects that the file path will be picked up by the config. But the client would want to keep this file in Blob storage etc. I think the better solution would be for this method to expect a byte[] stream for this certificate rather than reading it from configuration and let the client handle how they want to store it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the SoapClient RunTransaction() method and trace how it currently obtains the certificate path from configuration. The work would be complete when certificate bytes can be supplied by the client instead, allowing storage such as Blob storage without configuration, while preserving the existing request behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design, payments, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.