-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Every time a cookie is written, a call to the Crowd server is made. It'd be nice to cache this, but there are some serious issues to consider:
1- What if the domain on the Crowd & the webserver changes? If we cache the cookie domain, no-one will be able to log in until the cache expires.
2- Can we push updates of this sort of data to the client webserver?
- duplicates
-
CWD-3556 Allow for caching when retrieving cookie configurations (GET /config/cookie method)
- Closed
- is blocked by
-
CRUC-990 Create a review with multiple revisions of the same file or add multiple revisions of the same file via the manage files tab.
- Closed
- is cloned from
-
CWD-614 Implement caching on Crowd client layer
- Closed
[CWD-1037] Investigate caching the domain value for the cookie
Workflow | Original: JAC Suggestion Workflow [ 3388673 ] | New: JAC Suggestion Workflow 3 [ 3630763 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1389371 ] | New: JAC Suggestion Workflow [ 3388673 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Crowd Development Workflow v2 [ 273434 ] | New: Simplified Crowd Development Workflow v2 [ 1389371 ] |
Link | New: This issue is blocked by CRUC-7163 [ CRUC-7163 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] |
Workflow | Original: Feature Request Workflow [ 174416 ] | New: Crowd Development Workflow v2 [ 273434 ] |
Workflow | Original: jira [ 126351 ] | New: Feature Request Workflow [ 174416 ] |