Skip to main content
V
Vimal_Rawat14-Alexandrite
14-Alexandrite
June 15, 2022
Question

We need email of a user in a thing service but the email field in the user extension field is empty.

  • June 15, 2022
  • 1 reply
  • 2022 views

We are creating a service where we can send emails to users using a thing service. But the email field in the user extension does not have the user's email ID maintained. We have integration with azure, is it possible to get an email Id from Azure using a thing service? or is there any other way to retrieve the user's email ID?

1 reply

V
VladimirRosu_11662719-Tanzanite
19-Tanzanite
June 15, 2022

I strongly suggest implementing the storage of the user email address in the user extension field.

What kind of integration you have with Azure? SSO?

If so, you should have a way to setup this type of attribute quite easily.

 

    V
    Vimal_Rawat14-AlexandriteAuthor
    14-Alexandrite
    June 16, 2022

    We now have a lot of users on our platform and it is a tedious task to update user extensions for all the users manually.

    I am not sure if the integration with Azure is SSO enabled, but I can check that.

    In case we have Azure integration SSO enabled, will it be possible for the updating of the email in the user extension to be done by some scripts or any other way except for doing it manually.

    V
    VladimirRosu_11662719-Tanzanite
    19-Tanzanite
    June 16, 2022

    @Vimal_Rawat 

    I haven't suggested to do it manually in my email. Out of curiosity, what exactly do you mean by "integration with Azure" ? When I saw that I assumed you have either Directory Services or SSO with Azure. Can you also explain how users are created in your system?

    If you have SSO, with any provider, the user's email address is usually retrieved as an attribute, via configuration, and updated when the user logs in.

    I'm pretty sure that creating a script to have this update functionality is doable, but without more details around what is your specific infrastructure setup, it's hard to suggest anything.

      Terms & ConditionsAccessibility statement