linkedin / linkedin/ambry

Possible modification of SecurityService interface

Open
#392 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.8k
Forks
298
Avg merge
21h 43m
Merged PRs (30d)
9

Description

The API `public Future processRequest(RestRequest restRequest, Callback callback);` could be modified to take in an optional `BlobInfo` object (either as a new API or a modification to the current API) to avoid generating `BlobInfo` again in case it is required (this usually happens when certifying POST requests).

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

Locate the SecurityService interface and its processRequest(RestRequest, Callback) entry point, then trace where BlobInfo is generated during POST request certification. Compare the implications of an optional BlobInfo parameter versus a new API; done means the interface change and its callers are clearly specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.