Problem/Motivation

When using this in a CRM integration context, it is possible that the User is not yet know to Drupal.

Steps to reproduce

Have CRM integration where user does not exist in Drupal yet

Proposed resolution

Make the user retrieval a service so its logic can be modified by replacing the service. Site's can then extend the retrieval service as desired with own logic.

Remaining tasks

Convert to service

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Issue fork reset_password_email_otp-3490984

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

scott_euser created an issue. See original summary.

scott_euser opened merge request !29

scott_euser’s picture

scott_euser commented
Assigned: scott_euser » Unassigned
Status: Active » Fixed

  • scott_euser committed 269f7469 on 1.0.x 
    Issue #3490984 by scott_euser: Allow modifying the retrieved user during...

scott_euser opened merge request !31

  • scott_euser committed 753e3294 on 1.0.x 
    Issue #3490984 by scott_euser: Allow modifying the retrieved user during...
scott_euser’s picture

scott_euser commented

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.