As a Developer, I want to have a service provider of Pepper Storage to talk to a 3rd party storage of pepper

• Type: Story
• Status: Closed
• Priority: Minor
• Resolution: Discarded
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Application Security
• Labels:
  • 7.4
  • has_acceptance_criteria
• Epic Link: Crypto Hashing Library
• Sprint: AppSec Iteration 52, AppSec Iteration 53, AppSec Iteration 54, AppSec Iteration 55, AppSec Iteration 56, AppSec Iteration 57, AppSec Iteration 58, AppSec Iteration 59, AppSec Iteration 60, AppSec Iteration 61, AppSec Iteration 62, AppSec Iteration 63, AppSec Iteration 64
• Git Pull Request: https://github.com/liferay-appsec/liferay-portal/pull/198

Motivation

Pepper unlike salt, needs to be stored somewhere else other than along with password hash, for example, in a file or on Amazon cloud.
When a pepper is needed, we need to be able to fetch it from a file or Amazon cloud, as a result we need a service provider to allow different implementation of 3rd parties.

Acceptance Criteria

1. As a Developer, I want to have a service provider of Pepper Storage to talk to a 3rd party storage of pepper in order to be able to store and manage pepper on an external storage.