-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
Not defined
Which product and version do you currently use?
C8SM - Camunda Optimize 3.10.3
In which environments (staging, production, etc.) do you need the feature?
all
Please describe the missing/desired functionality:
Make response header size configurable
What problem would the feature solve?
The response header size depends on the used environment as a Set-Cookie header for the X-Optimize-Authorization which contains a JWT is set on the first interaction with Optimize.
What effort would be required without the feature?
The token would have to be kept small enough to not exceed 8kb header in total
Do you have a deadline by which you need this feature?
asap
Why do you need this feature?
So that users with many rights (which leads to a big token) can still login.
Who benefits from the feature (developers, end users, management) and how big is the respective group?
end users: they can login
developers: they can configure the header size if required
How would not implementing the feature impact you?
Users with big token could not login
This is the controller panel for Smart Panels app
[OPT-7210] Make Response Header size configurable
| Link | New: This issue is related to SUPPORT-17768 [ SUPPORT-17768 ] |
| Summary | Original: WIP-FR | New: Make Response Header size configurable |
| Description |
Original:
h3. Which product and version do you currently use?
h3. In which environments (staging, production, etc.) do you need the feature? h3. Please describe the missing/desired functionality: h3. What problem would the feature solve? h3. What effort would be required without the feature? h3. Do you have a deadline by which you need this feature? h3. Why do you need this feature? h3. Who benefits from the feature (developers, end users, management) and how big is the respective group? h3. How would not implementing the feature impact you? |
New:
h3. Which product and version do you currently use?
C8SM - Camunda Optimize 3.10.3 h3. In which environments (staging, production, etc.) do you need the feature? all h3. Please describe the missing/desired functionality: Make response header size configurable h3. What problem would the feature solve? The response header size depends on the used environment as a Set-Cookie header for the X-Optimize-Authorization which contains a JWT is set on the first interaction with Optimize. h3. What effort would be required without the feature? The token would have to be kept small enough to not exceed 8kb header in total h3. Do you have a deadline by which you need this feature? asap h3. Why do you need this feature? So that users with many rights (which leads to a big token) can still login. h3. Who benefits from the feature (developers, end users, management) and how big is the respective group? end users: they can login developers: they can configure the header size if required h3. How would not implementing the feature impact you? Users with big token could not login |
| Labels | New: SUPPORT |
| Assignee | New: Joshua Windels [ joshua.windels ] |
| Assignee | Original: Joshua Windels [ joshua.windels ] | New: Helene Waechtler [ helene.waechtler ] |
| Status | Original: Triage [ 10612 ] | New: In Review [ 10212 ] |
| Assignee | Original: Helene Waechtler [ helene.waechtler ] | New: Giuliano Rodrigues Lima [ giuliano.rodrigues-lima ] |
| Fix Version/s | New: 3.11.0-alpha5 [ 18493 ] |
| Fix Version/s | New: 3.9.6 [ 18492 ] | |
| Fix Version/s | New: 3.10.6 [ 18495 ] |
| Fix Version/s | Original: 3.9.6 [ 18492 ] |