[Extensibility Request] Add missing RSACryptoServiceProvider wrapper methods
Nobody has claimed this yet.
- Dominant language
- AL
- Stars
- 683
- Forks
- 459
- Avg merge
- 3d 26m
- Merged PRs (30d)
- 633
Description
Describe the issue
When using a 3rd party public key provided to encrypt data before sending it to an API, it is currently seemingly impossible to encrypt anything, if the public key is not available as XML string.
Currently, what I would consider missing is that we would - at a minimum - require the method "ImportFromPem" to be exposed in the codeunit. This would then allow importing the actual public key and then existing methods should be able to be used for the actual encryption.
Expected behavior
It should be possible to create an instance of a RSACryptoServiceProvider to store an external public key.
Steps to reproduce
N/A
Additional context
No response
I will provide a fix for a bug
- I will provide a fix for a bug
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the RSACryptoServiceProvider codeunit and review its existing key-import and encryption methods. Confirm how wrapper methods are exposed, then verify that a PEM public key can be imported and used by the existing encryption flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100