-
Notifications
You must be signed in to change notification settings - Fork 16
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
LUPEYALPHA 1171/identity task #3359
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
from
October 31, 2024 12:07
bc25e8b
to
65e480c
Compare
rjlynch
added
deploy
Deploy a review app for this PR
and removed
deploy
Deploy a review app for this PR
labels
Oct 31, 2024
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
from
October 31, 2024 13:43
65e480c
to
b18b869
Compare
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
from
October 31, 2024 13:53
b18b869
to
b3d4a64
Compare
rjlynch
changed the title
LUPEYALPHA 1171/identity task 1
LUPEYALPHA 1171/identity task
Oct 31, 2024
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
2 times, most recently
from
October 31, 2024 16:01
e20cc58
to
a8c1906
Compare
asmega
approved these changes
Nov 1, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 👍 👍
Allow a policy to define it's own view for a specific task. If a policy defines a template `admin/tasks/<policy name>/tasks/<task name>` we'll use that when rendering the task view. If there isn't a policy specific view we'll fall back to the task view in `admin/tasks/<taske name>`.
Previously we were not running the claim verifiers for EY as EY claims don't have a trn. This commit passes in a nil dqt teacher status if the policy doesn't have a trn but still runs the claim verifiers.
This allows us some controller if we want to stub this in our tests
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
from
November 1, 2024 15:30
a8c1906
to
dca5334
Compare
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
from
November 1, 2024 15:50
dca5334
to
ee28fb4
Compare
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
from
November 1, 2024 15:59
ee28fb4
to
e00f8ed
Compare
This task displays differently to other tasks as such we've introduced a separate claim verifier and separate view template.
This is the same warning but it now has a different fingerprint as we've move some of the lines of code around.
rjlynch
force-pushed
the
LUPEYALPHA-1171/identity-task-1
branch
from
November 1, 2024 16:07
e00f8ed
to
f4bf844
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Might be easier to review each commit separately.
The main change in this pr is adding the Identity task.
The EY identity task behaves slightly differently to the other tasks.
EY practitioners don't have DQT records so we're only using the information
from one login to check identity, additionally the rules around creating the
task are slightly different to other policies.
If the one login check passes and the name returned from OL matches the name
the provider entered the task is a pass
If the one login check passes and the names are a partial match¹ then we
create task with a partial match (see Admin::ClaimsHelper#task_status_tag)
If the one login check passes and the name from OL is different to the
provider supplied name we create a failed task.
If the one login check fails we create a failed task.
If the task is a partial match we render the task form for admins to update the
task (either passing or failing it).
Another quirk is if the practitioner hasn't completed their portion of the
journey we don't want to render the task form, and instead we want to show some
copy informing admins the practitioner is yet to complete their journey.
As there's a few differences between how other identity tasks work we've
introduced a separate task view for EY identity tasks.
¹ - we'll be changing the rules around what counts as a partial match in a
separate ticket.