Skip to content

Include user's email address in Telesign Intelligence API request

What does this MR do and why?

Related to https://gitlab.com/gitlab-org/modelops/anti-abuse/team-tasks/-/issues/753 and https://gitlab.com/gitlab-org/modelops/anti-abuse/team-tasks/-/issues/735

This MR updates the payload of Telesign Intelligence API request to include the user's email address.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Sample log now with telesign_risk_score

{
  "severity": "INFO",
  "time": "2024-06-06T05:50:18.076Z",
  "correlation_id": "01HZP1J3TP3KD9RBTBKG23Q6P9",
  "meta.caller_id": "Users::RegistrationsIdentityVerificationController#send_phone_verification_code",
  "meta.remote_ip": "127.0.0.1",
  "meta.feature_category": "instance_resiliency",
  "meta.client_id": "ip/127.0.0.1",
  "class": "PhoneVerification::TelesignClient::RiskScoreService",
  "message": "IdentityVerification::Phone",
  "event": "Received a risk score for a phone number from Telesign",
  "telesign_reference_id": "363FB064513C0B1C93037E47E4B064E8",
  "telesign_response": "Transaction successfully completed",
  "telesign_status_code": "200",
  "telesign_risk_score": 141,
  "username": "jun2451045"
}

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Edited by Eugie Limpin

Merge request reports

Loading