apigee-edge-drupal
apigee-edge-drupal copied to clipboard
Error sending email with capitalization to Apigee.
Description
Our organization is using SSO to log users into the developer portal. This creates a user in Drupal, and our identity provider is sending over the users email address. The email address gets saved with proper capitalization, so I am [email protected]
. When the module takes this user and create them as a developer in Apigee, we are getting an error that email address must be lower case.
Expected Behavior
I would expect that a Developer get created on the Apigee side.
Screenshots
Notes
I guess I would suggest that all users get set/synced to apigee with a lowercase email address.
Version Info
Drupal core 9.4.5 Apigee_edge 2.0.4 DevPortal_Kickstart 2.1.0
Hi @dpagini
Could you please tell us which Apigee Organization you are using, are you using Apigee Edge
or Apigeex
?
Apigee X (Endpoint: https://apigee.googleapis.com/v1)
Hi @dpagini , Thank you for raising this issue. Yes, Apigeex Org is not accepting capitalized email addresses and Drupal portal does.
We are investigating this issue, We will keep you posted on any further update.
Thanks. I would think that, the controller responsible for calling Apigee simply needs to perform a lowercase conversion on the user email before sending to Apigee?
If you are able to provide a patch or diff, I'm happy to help test out. Thank you @shishir-intelli!
Thanks @dpagini Sure, We are working on this issue, I will share a patch as soon as it's resolved.
Hi @dpagini
Apologies for the delayed response.
To fix this issue, we decided to lower-case the email address for Apigee-X Org due to case sensitive restrictions. I have attached a patch which fixes this issue. patch_730_1.txt
Please try this patch and let me know if this resolves your issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I feel like this issue shouldn't be closed as there is still an open PR for this issue...? And that PR definitely has open conversations around approach...
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.