Show verification and profile columns and request verification in IAM - #36
Merged
Merged
Conversation
…in IAM
- Users list columns:
- Email Verified and Phone Verified, with a Verified/Unverified badge
(verified date as tooltip) and a verified/unverified filter;
- Country, Timezone, Date of Birth and IP Address, hidden by default in
the column picker, with country and timezone filters.
- Row actions, each shown only when that email/phone is set and not
verified (`iam verify user`): Send email verification, Send phone
verification, Mark email verified, Mark phone verified. They replace
the single "Verify user", which only covered email.
- user-actions: sendVerification() sends the user a one-click link
(fleetbase/core-api#267). markVerified() marks a channel verified.
verifyUser() keeps working as markVerified(user, 'email').
This file contains hidden or 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
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.
Why
In IAM an admin could only Verify user, which marks the email verified. They couldn't:
Several useful fields the API already returns weren't shown either.
Changes
table/cell/verification-statuscell shows a Verified badge (verified date in the tooltip), Unverified, or a dash when there's no email/phone. Each has a Verified/Unverified filter (email_verified,phone_verified).iam verify user, each shown only when that email/phone is set and unverified):user-actionsservice: newsendVerification(user, channel)andmarkVerified(user, channel).verifyUser()still works and marks the email verified, so other engines calling it are unaffected.Depends on
send-verificationendpoint, thechannelparam onusers/verify, and the new filters.auth/verify-contactpage the link opens.This touches the same users controller and translations as #35, so expect a small conflict on the
queryParamsline: #35 dropstype, and this adds four params.Testing