[MGNLREST-336] Fix slow BasicAuth performance Created: 17/Nov/21  Updated: 31/Jan/22  Resolved: 19/Jan/22

Status: Closed
Project: Magnolia REST Framework
Component/s: None
Affects Version/s: 2.2.8
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Roberto Gaona Assignee: Javier Benito
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File apiRequestExample.sh     Text File curl-format.txt    
Issue Links:
Problem/Incident
Relates
dependency
depends upon MGNLREST-71 Rest authentication with API Tokens o... Accepted
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: DevX 1
Story Points: 5

 Description   

Timebox to 5 SP to look for cause of issue.

If issue is too expensieve we will probably not fix in favor of planned token-based authentication

Steps to reproduce

  1. Enable BasicAuth for your REST requests
  2. Perform calls in a bulk (Nodes API, per example)

Expected results

Requests take the usual time to be completed.

Actual results

Due to BasicAuth, an average of 200-300ms is added per request, vastly increasing the time it takes to complete the bulk of calls.

Workaround

Development notes



 Comments   
Comment by Christopher Zimmermann [ 04/Jan/22 ]

Is it possible to improve the performance of the auth? "Due to BasicAuth, an average of 200-300ms "

Generated at Mon Feb 12 06:58:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.