-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FI-2787: AuthInfo input skeleton #503
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #503 +/- ##
==========================================
- Coverage 79.70% 79.47% -0.24%
==========================================
Files 240 242 +2
Lines 11927 12080 +153
Branches 1169 1185 +16
==========================================
+ Hits 9506 9600 +94
- Misses 1757 1815 +58
- Partials 664 665 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
I'm ok with this approach for now. |
@arscan Could you approve the PR then? |
fc968e1
to
f76ccc0
Compare
Summary
This branch provides an initial skeleton for a new type of input called
auth_info
. The goals for this input type are to consolidate all of the information needed to perform authorization, use that authorization to access resources, and refresh the authorization into a single location.The intent is for the UI for this input type to be dynamic so that only the fields necessary for the particular scenario are displayed to the user. This will be accomplished through several means:
mode
option with the following possible values:auth
- this will present all of the input fields required in order to perform an initial authorizationaccess
- this will present the access token, as well as the fields required to refresh that access token, for tests which are accessing resources based on a prior authorization.use_discovery
checkbox in auth mode. When checked, the fields which can be found via a discovery endpoint will not be displayed to the user.auth_type
field allows the user (or the test writer) to select which auth workflow will be used, so that only the fields relevant to that particular workflow are displayed.This branch does not implement the actual use of the
auth_info
input type, but exposes examples through the JSON API to support front end development for this feature.Testing Guidance
There is a new auth info suite which containts tests with default input values for each of the modes and auth types. Since the UI for this input type is not yet implemented, the inputs will appear as text inputs. The tests will verify that the received inputs are what is expected, so as the UI is developed, they can be used to validate the UI behavior.