Feature #8863: Add tenantName logic related to sec_authentication_domain in FWD - Runtime Infrastructure - Golden Code Redmine

Feature #8863

Add tenantName logic related to sec_authentication_domain in FWD

Added by Radu Apetrii about 2 years ago. Updated 5 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Ovidiu Maxiniuc

Target version:

Start date:

Due date:

% Done:

100%

billable:

vendor_id:

GCD

case_num:

version_reported:

version_resolved:

reviewer:

Radu Apetrii

production:

env_name:

topics:

Multi Tenant

History

#1 Updated by Radu Apetrii about 2 years ago

The purpose of this task is to add the tenantName logic that is related to the sec_authentication_domain table in FWD.
Currently, SecurityOps.WorkArea.addDomain is the method that handles domain creation. In here, there are multiple columns set, but tenantName is not amongst them.
In terms of implementation, at least for the start, the following things need to be done:

When creating a domain, specify the tenant for which the domain is created.
When a tenant tries to access a domain, check if the domain is valid (can be assigned to that tenant).
In SecurityOps.readDomains, retrieve the tenant name from the sec_authentication_domain.

#3 Updated by Eric Faulhaber about 2 years ago

Project changed from Base Language to Runtime Infrastructure

#4 Updated by Eric Faulhaber over 1 year ago

Assignee set to Ovidiu Maxiniuc
Priority changed from Normal to High
reviewer Radu Apetrii added

#5 Updated by Radu Apetrii over 1 year ago

Some notes about the three bullets from #8863-1:

Bullet 1: This most probably means adding another parameter to SecurityOps$WorkArea.addDomain() which resembles the tenant name. Also, in SecurityOps$Domain, we'll probably need another field, tenantName.
Bullet 2: Now that I'm re-reading bullet 2, I think I made a mistake when writing it. Basically, we give the domain name, and only after that we know which tenant was selected. We don't know in advance the tenant name so that we can check against the domain's tenant name.
- So, assuming I haven't missed anything obvious here, I believe this bullet can be skipped.
Bullet 3: The SQLs from SecurityOps.readDomains need to be updated to contain the tenantName column as well.

Depending on what we discover while implementing this feature, or some customer requests that may appear, the notes might suffer some changes. For now, I think bullets 1 and 3 are a good starting point.