From c7eb71c4ad66981484f9f5846437628a165622cd Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Fri, 1 Apr 2022 17:29:25 +0200 Subject: [PATCH] notes/cisco_ft_securex_registration.org --- notes/cisco_ft_securex_registration.org | 4 ---- 1 file changed, 4 deletions(-) diff --git a/notes/cisco_ft_securex_registration.org b/notes/cisco_ft_securex_registration.org index 16ce589d..3b868684 100644 --- a/notes/cisco_ft_securex_registration.org +++ b/notes/cisco_ft_securex_registration.org @@ -36,7 +36,6 @@ - [[#canceled-optional-hide-matching-org][CANCELED /OPTIONAL/ Hide Matching Org]] - [[#redirects-user][Redirects User]] - [[#1-optional-sync-useridentity-on-all-successful-securex-login][=1= /OPTIONAL/ Sync UserIdentity on all successful SecureX login]] - - [[#ui-for-the-orgaccessrequest-approvalreject-page][UI for the ~OrgAccessRequest~ Approval/Reject page]] - [[#3-email-notification-of-org-request-accesses][=3= Email Notification of Org Request Accesses]] - [[#notes][Notes]] - [[#2-org-requests-crud-api-for-admins-of-the-orgs][=2= Org Requests CRUD API for Admins of the Orgs]] @@ -716,9 +715,6 @@ From #6076 we have a new CRUD service that should keep track of `UserIdentity`. Mainly this information could be used as providing more details than what is currently set int he user's `idp-mapping`. Typically we have access to the email of the UserIdentity, user name from the IdP, and probably a lot more details that will be useful. So every time a successful login occurs we should update the UserIdentity object last logged in date (as we do for users) which will probably be quite useful. -*** UI for the ~OrgAccessRequest~ Approval/Reject page - -M ** =3= Email Notification of Org Request Accesses /Estimate: 3 rcd after email+html templates/