notes/cisco_ft_securex_registration.org
This commit is contained in:
parent
b8f7fc9243
commit
c7eb71c4ad
1 changed files with 0 additions and 4 deletions
|
@ -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/
|
||||
|
|
Loading…
Reference in a new issue