[MGNLTEST-348] Facilitate saas-tf local testing environment setup Created: 10/Nov/22 Updated: 23/Dec/22 |
|
| Status: | Open |
| Project: | Magnolia Test Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Roberto Gomez | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoR: |
Empty
|
||||||||||||
| Epic Link: | subscription-life-cycle-support-by-test-fwk | ||||||||||||
| Team: | |||||||||||||
| Description |
|
Saas test framework setup for local testing can be configured with the developer OKTA user for subscription service request, but it requires common OKTA token granted application credentials. We need to failitate any developer to setup their local testing environment without needing to share any sensible credentials. Is there any OKTA functionality allowing this? Do we need to implement a custom auth proxy? Aside from credentials for saas-tf, the developer also needs to setup selenium, which is done by means of a docker image and credential setup may be needed as well (see
All this should be documented and make accesible to the developers.
|