-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Context:
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate what the BE should default to instead (<default> tenant? List of all available tenants? list of all user authorised tenants?) . While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation):
This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts.
- creation of management entities - not required, already defaults to authorized tenants only
- creation of instant preview dashboard - not required, already defaults to authorized tenants only
- definition retrieval for notification sending - tenant selection irrelevant, adjusted with
OPT-7124 - definition name retrieval for email sending - tenant selection irrelevant, adjusted with
OPT-7124 - DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants.
DEFAULT_TENANT_IDS) - not required, Optimize should already be able to handle all scenarios if there is no null tenant - TBC
ATs:
- above list is completed during implementation with where the logic is and what we are changing it to
- testing notes are compiled according to the above list
- IT are adjusted if required
- if these changes lead to any significant changes in Optimize behaviour a separate docs ticket is opened
Testing Notes
- to be written during implementation
This is the controller panel for Smart Panels app
[OPT-7165] Adjust BE for C8 resources with tenant ID
| Description |
New:
Since CCSM now will become tenant aware, we need to adjust the process overview endpoint so that it doesnt return tenants for which the user has no authorization for. This needs to happen after we fetch from identity all the tenants which the user has access to.
ATs: - The process overview endpoint only returns definitions which belogn to the tenant a user has access to. - The are ITs to verify this behavior |
| Status | Original: Triage [ 10612 ] | New: Backlog [ 11212 ] |
| Summary | Original: Adjust process overview so that only tenants a user has authorization for appear | New: Adjust BE for C8 resources without tenant ID |
| Description |
Original:
Since CCSM now will become tenant aware, we need to adjust the process overview endpoint so that it doesnt return tenants for which the user has no authorization for. This needs to happen after we fetch from identity all the tenants which the user has access to.
ATs: - The process overview endpoint only returns definitions which belogn to the tenant a user has access to. - The are ITs to verify this behavior |
New:
*Context:*
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate if the BE has to default to the <default> tenant or to an empty list or to a list filled with user specific tenants. While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation): _This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts._ * creation of management entities * creation of instant preview dashboard * definition retrieval for notification sending * DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants. DEFAULT_TENANT_IDS) * TBC *ATs:* - above list is completed during implementation with where the logic is and what we are changing it to - testing notes are compiled according to the above list - IT are adjusted if required |
| Description |
Original:
*Context:*
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate if the BE has to default to the <default> tenant or to an empty list or to a list filled with user specific tenants. While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation): _This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts._ * creation of management entities * creation of instant preview dashboard * definition retrieval for notification sending * DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants. DEFAULT_TENANT_IDS) * TBC *ATs:* - above list is completed during implementation with where the logic is and what we are changing it to - testing notes are compiled according to the above list - IT are adjusted if required |
New:
*Context:*
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate if the BE has to default to the <default> tenant or to an empty list or to a list filled with user specific tenants. While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation): _This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts._ * creation of management entities * creation of instant preview dashboard * definition retrieval for notification sending * DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants. DEFAULT_TENANT_IDS) * TBC *ATs:* - above list is completed during implementation with where the logic is and what we are changing it to - testing notes are compiled according to the above list - IT are adjusted if required - if these changes lead to any significant changes in Optimize behaviour a separate docs ticket is opened |
| Description |
Original:
*Context:*
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate if the BE has to default to the <default> tenant or to an empty list or to a list filled with user specific tenants. While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation): _This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts._ * creation of management entities * creation of instant preview dashboard * definition retrieval for notification sending * DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants. DEFAULT_TENANT_IDS) * TBC *ATs:* - above list is completed during implementation with where the logic is and what we are changing it to - testing notes are compiled according to the above list - IT are adjusted if required - if these changes lead to any significant changes in Optimize behaviour a separate docs ticket is opened |
New:
*Context:*
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate if the BE has to default to the <default> tenant or to an empty list or to a list filled with user specific tenants. While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation): _This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts._ * creation of management entities * creation of instant preview dashboard * definition retrieval for notification sending * DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants. DEFAULT_TENANT_IDS) * TBC *ATs:* - above list is completed during implementation with where the logic is and what we are changing it to - testing notes are compiled according to the above list - IT are adjusted if required - if these changes lead to any significant changes in Optimize behaviour a separate docs ticket is opened *Testing Notes* * to be written during implementation |
| Description |
Original:
*Context:*
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate if the BE has to default to the <default> tenant or to an empty list or to a list filled with user specific tenants. While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation): _This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts._ * creation of management entities * creation of instant preview dashboard * definition retrieval for notification sending * DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants. DEFAULT_TENANT_IDS) * TBC *ATs:* - above list is completed during implementation with where the logic is and what we are changing it to - testing notes are compiled according to the above list - IT are adjusted if required - if these changes lead to any significant changes in Optimize behaviour a separate docs ticket is opened *Testing Notes* * to be written during implementation |
New:
*Context:*
There are a few places in the BE where tenant logic has been ignored for C8 since multi tenancy was not available in C8. In each case we need to evaluate what the BE should default to instead (<default> tenant? List of all available tenants? list of all user authorised tenants?) . While they may be unrelated this ticket aims to address all of these places to avoid requiring specific tickets per case. The following spots need adjusted (list to be kept up to date during implementation): _This list is not yet complete - as a first step during implementation we need to scan the BE for other relevant parts._ * creation of management entities * creation of instant preview dashboard * definition retrieval for notification sending * DTO initialisation for reports, collectionscopes, requestDTOs (anywhere we currently use ReportConstants. DEFAULT_TENANT_IDS) * TBC *ATs:* - above list is completed during implementation with where the logic is and what we are changing it to - testing notes are compiled according to the above list - IT are adjusted if required - if these changes lead to any significant changes in Optimize behaviour a separate docs ticket is opened *Testing Notes* * to be written during implementation |
| Component/s | New: backend [ 13653 ] |
| Status | Original: Backlog [ 11212 ] | New: Ready [ 10005 ] |