Description
As a [user/developer/hosting service] I want to [be able to ...] so that [I can implement ... / I can host / I can send/...]. This can be achieved by [changes in the ...-layer / adding a specific functionality]
Currently the CLI enforces being logged in. We should also add a security layer in the application layer. We can achieve this by switching the methodsingatur of each Address to the authUseCase.
Another possible solution would be to provide the authUseCase to an AbstractAuthorizedService. Every other Service will extend this AbstractAuthorizedService and has to provide the authUseCase via the super(authUseCase) constructor. On each action, the AbstractAuthorizedService should ensure the logged in state.
We could either switch the CLI to not care about the authorization or we could implement the application layer security on top. I think its best if we switch out the security aspect in the CLI for better decoupling
Ready Criteria
[ ] everyone understood the scope of this ticket
[ ] effects in domain- / useCase- / external-layers are discussed
[ ] atleast one person is assigned
Acceptance Criteria
[ ] CLI does not care anymore about being authorized or not
[ ] ApplicationLayer services which requires a login extend AbstractAuthorizedService
Scope
[ ]
Additional context
Add any other context or screenshots about the feature request here.
Description As a [user/developer/hosting service] I want to [be able to ...] so that [I can implement ... / I can host / I can send/...]. This can be achieved by [changes in the ...-layer / adding a specific functionality] Currently the CLI enforces being logged in. We should also add a security layer in the application layer. We can achieve this by switching the methodsingatur of each Address to the authUseCase.
Another possible solution would be to provide the authUseCase to an AbstractAuthorizedService. Every other Service will extend this AbstractAuthorizedService and has to provide the authUseCase via the super(authUseCase) constructor. On each action, the AbstractAuthorizedService should ensure the logged in state.
We could either switch the CLI to not care about the authorization or we could implement the application layer security on top. I think its best if we switch out the security aspect in the CLI for better decoupling
Ready Criteria
Acceptance Criteria
Scope
Additional context Add any other context or screenshots about the feature request here.