From 89d9585fb21c7eab96e8557556e08634625713b9 Mon Sep 17 00:00:00 2001 From: Oren Mittman Date: Fri, 6 Sep 2024 22:16:38 -0400 Subject: [PATCH] [ARP-86023] ARP IPF: Correct controller logic for `user.verified`. --- .../v0/representative_users_controller.rb | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/modules/accredited_representative_portal/app/controllers/accredited_representative_portal/v0/representative_users_controller.rb b/modules/accredited_representative_portal/app/controllers/accredited_representative_portal/v0/representative_users_controller.rb index 7f8f67e1687..201daaeafc6 100644 --- a/modules/accredited_representative_portal/app/controllers/accredited_representative_portal/v0/representative_users_controller.rb +++ b/modules/accredited_representative_portal/app/controllers/accredited_representative_portal/v0/representative_users_controller.rb @@ -14,7 +14,7 @@ def show profile: { first_name: @current_user.first_name, last_name: @current_user.last_name, - verified:, + verified: @current_user.user_account.verified?, sign_in: { service_name: @current_user.sign_in[:service_name] } @@ -26,13 +26,6 @@ def show private - def verified - # TODO: Should we make this a genuine derivation of the user's LOA? The - # source of truth of the fact that ARP's users are always verified is - # ARP's `SignIn::ClientConfig` which requires such a high LOA level. - true - end - def in_progress_forms InProgressForm.for_user(@current_user).map do |form| {