adobe / adobe/frl-online-proxy
Enable passing additional activation data to the server
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
The FRL Online package controls which local device parameters (e.g., local OS device name or network hostname) are sent to the server. The proxy currently will currently ignore these parameters, so when used in store/forward mode it won't actually pass this info to the server (and these parameters won't be available in the local database). To date this hasn't been an issue, since no packages send these parameters, but customers are asking to be able to report this information, so we should make sure the proxy handles them.
Describe the solution you'd like
The proxy should capture all parameters sent by the device, not just those that are required for activation to succeed. It should be storing these in the local database and sending them to the server when requests are forwarded.
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
Start by tracing the proxy's activation request handling, local database storage, and store/forward forwarding paths. Confirm how required activation parameters are currently selected, then verify that all device parameters are stored locally and sent to the server when requests are forwarded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100