-
Suggestion
-
Resolution: Low Engagement
-
None
-
5
-
Summary
When cookie.tokenkey is missing in product's crowd.properties the value will be pulled from Crowd's /rest/config/cookie endpoint every time authentication check happens.
cookie.tokenkey is an optional configuration and it should be safe to not define it, but at the same time it adds a lot of unnecessery communication load. Making it cached on server side for few minutes could address this problem.
Workaround
Set the cookie.tokenkey to the value configured in the Crowd server. This is detailed in The crowd.properties file. Specifically:
An example of this configuration:
... cookie.tokenkey=crowd.token_key
[CWD-5250] Cache cookie.tokenkey pulled from Crowd's /rest/config/cookie
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Future Consideration [ 11775 ] | New: Closed [ 6 ] |
Labels | New: cleanup-seos-fy25 |
Support reference count | New: 5 |
Remote Link | New: This issue links to "Page (Confluence)" [ 463432 ] |
Workflow | Original: JAC Suggestion Workflow [ 3387890 ] | New: JAC Suggestion Workflow 3 [ 3631047 ] |
Status | Original: Under Consideration [ 11774 ] | New: Future Consideration [ 11775 ] |
Component/s | New: Authentication / Security [ 12726 ] |
Description |
Original:
h3. Summary
When {{cookie.tokenkey}} is missing in product's {{crowd.properties}} the value will be pulled from Crowd's {{/rest/config/cookie}} endpoint every time authentication check happens. {{cookie.tokenkey}} is an optional configuration and it should be safe to not define it, but at the same time it adds a lot of unnecessery communication load. Making it cached on server side for few minutes could address this problem. h3. Workaround Set the {{cookie.tokenkey}} to the value configured in the Crowd server. This is detailed in [The crowd.properties file|https://confluence.atlassian.com/display/CROWD/The+crowd.properties+file]. Specifically: An example of this configuration: {code:XML} ... cookie.tokenkey crowd.token_key {code} |
New:
h3. Summary
When {{cookie.tokenkey}} is missing in product's {{crowd.properties}} the value will be pulled from Crowd's {{/rest/config/cookie}} endpoint every time authentication check happens. {{cookie.tokenkey}} is an optional configuration and it should be safe to not define it, but at the same time it adds a lot of unnecessery communication load. Making it cached on server side for few minutes could address this problem. h3. Workaround Set the {{cookie.tokenkey}} to the value configured in the Crowd server. This is detailed in [The crowd.properties file|https://confluence.atlassian.com/display/CROWD/The+crowd.properties+file]. Specifically: An example of this configuration: {code:XML} ... cookie.tokenkey=crowd.token_key {code} |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 2812479 ] | New: JAC Suggestion Workflow [ 3387890 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Verified [ 10005 ] | New: Under Consideration [ 11774 ] |
Status | Original: Open [ 1 ] | New: Verified [ 10005 ] |