-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
1
-
S
When a user is added to the collection in SaaS mode, a text string can be entered to find that user. If the user doesn't match a search result in Optimze's cache, the request is forwarded to the accounts service. However, this doesn't make sense as cloud users can never know their ID, and the ID is the only means for retrieving users at this endpoint.
Optimize should instead not allow this secondary fetching, and only allow the addition of users that do exist in the cache.
Notes:
- These requests were highlighted as erroneous by the cloud team. In the case of many requests, it could even cause an issue of preventing use of the accounts service
- The implication of this change is that users can only be added to a collection if they do exist in a cache. New users may have to wait until the cache is repopulated before they are granted access to collections
- If these requests are shown to be causing problems, it might be that we need to provide a patch for this going forward
This is the controller panel for Smart Panels app
[OPT-6136] Remove accounts service fallback request on cache miss
| Status | Original: Open [ 1 ] | New: In Development [ 10312 ] |
| Description |
Original:
When a user is added to the collection in SaaS mode, a text string can be entered to find that user. If the user doesn't match a search result in Optimze's cache, the request is forwarded to the accounts service. However, this doesn't make sense as cloud users can never know their ID, and the ID is the only means for retrieving users at this endpoint.
Optimize should instead not allow this secondary fetching, and only allow the addition of users that do exist in the cache. *Notes:* * These requests were highlighted as erroneous by the cloud team. In the case of many requests, it could even cause an issue of preventing use of the accounts service * The implication of this change is that users can only be added to a collection if they _do_ exist in a cache. New users may have to wait until the cache is repopulated before they are granted access to collections |
New:
When a user is added to the collection in SaaS mode, a text string can be entered to find that user. If the user doesn't match a search result in Optimze's cache, the request is forwarded to the accounts service. However, this doesn't make sense as cloud users can never know their ID, and the ID is the only means for retrieving users at this endpoint.
Optimize should instead not allow this secondary fetching, and only allow the addition of users that do exist in the cache. *Notes:* * These requests were highlighted as erroneous by the cloud team. In the case of many requests, it could even cause an issue of preventing use of the accounts service * The implication of this change is that users can only be added to a collection if they _do_ exist in a cache. New users may have to wait until the cache is repopulated before they are granted access to collections * If these requests are shown to be causing problems, it might be that we need to provide a patch for this going forward |
| Assignee | Original: Joshua Windels [ joshua.windels ] | New: Sebastian Bathke [ sebastian.bathke ] |
| Status | Original: In Development [ 10312 ] | New: In Review [ 10212 ] |
| Assignee | Original: Sebastian Bathke [ sebastian.bathke ] | New: Helene Waechtler [ helene.waechtler ] |
| Assignee | Original: Helene Waechtler [ helene.waechtler ] | New: Joshua Windels [ joshua.windels ] |
| Status | Original: In Review [ 10212 ] | New: Rework [ 11413 ] |
| Status | Original: Rework [ 11413 ] | New: In Development [ 10312 ] |
| Assignee | Original: Joshua Windels [ joshua.windels ] | New: Cigdem Ilhan [ cigdem.ilhan ] |
| Status | Original: In Development [ 10312 ] | New: In Test [ 10004 ] |
| Fix Version/s | New: 3.8.1 [ 17690 ] | |
| Fix Version/s | New: 3.9.0 [ 17691 ] |
| Assignee | Original: Cigdem Ilhan [ cigdem.ilhan ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Test [ 10004 ] | New: Done [ 10010 ] |
| Fix Version/s | New: 3.9.0-preview-1 [ 17711 ] |