Do proof of concecpt for using the AO (Institution ID) for identifying tenants when IP address is shared among tenants.

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

Preliminary investigation indicates that using AO might be a clean easy to provide a solution. This ticket will explore that by creating a POC that passes AO in every request and identifies the tenant that way.

Environment

None

Potential Workaround

None

Checklist

hide

Activity

Show:

Gurleen Kaur1 July 22, 2024 at 12:04 PM

The current implementation cannot accommodate passing different AO values on the same IP/connection without significant changes. The core issue is obtaining a correct token, as there isn't enough information to do so. While passing in a username and password could technically resolve this, it is an undesirable and inelegant solution. Therefore, the best course of action is to stick with the original idea of incorporating a port number. This approach should be effective, as the AO solution proves to be unhelpful in this context.
Creating another Jira for trying out the port number POC.
CC :

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Volaris

Affected Institution

!!!ALL!!!

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created June 28, 2024 at 3:01 PM
Updated July 22, 2024 at 12:04 PM
Resolved July 22, 2024 at 12:04 PM
TestRail: Cases
TestRail: Runs