New Topic

Community Topic Problem Administration

Deepak Chaganti

Yellowfin Support Team

Assigned

Category Administration

Product Version 9.0

Rest/Api: Removing a user's email seems not work

Stefan Hall shared this problem ago

Resolved

Hello,

I send a request against the rest/api according to the documentation:
https://developers.yellowfinbi.com/dev/api-docs/current/#operation/updateUserAdmin

If I set PATCH with {"emailAddress": ...

null }, I received 200 OK, but email ist NOT cleared/deleted
""}, I received 400 Bad Request

if I change the email together with the first name, only the first name is changed (in the 200 OK case). Unfortunately, it looks like another API error to me ;(

;) Stefan

Version 9.13

The same problem 0

Replies (4)

Deepak Chaganti ●

Hello Stefan,

My name is Deepak Chaganti from the Yellowfin Technical Support Team. We have received your support request, and I will be your primary contact on the following ticket:

Ticket Number: #31465
Case Title: Rest/Api: Removing a user's email seems not work

Thanks for sharing the details.

Could you please confirm if our main goal here is to remove the email address of an admin user ? or change the email address of the user?

I will try to perform the same operation in Postman on my end.

Sincerely,

Deepak Chaganti

Yellowfin Technical Support Engineer

Reply URL

Deepak Chaganti ●

Hi Stefan,

Yes, that is correct.

Even in the UI, we won't be able to leave the email field as 'null':

0934ea85be5ecab14f9e98e0298dd967

Could you please let us know the actual requirement of saving email as null so that I can discuss the business requirement with the wider team?

Thanks,

Deepak

Reply URL

Stefan Hall ●

Hi Deepak,

The use case is quickly explained: we need to synchronize the personal data in all systems with our central HR system. If the user does not have an email there or the email address has been removed (for whatever reason), this must also be done in all other systems.

I would also set the email to an empty string, but then I get a 400 bad request ;)

Fortunately, you use the userid for the registration process and not the email address.

;) Stefan

URL

Deepak Chaganti ●

Hi Stefan,

I have reached out to the wider team with the use case scenario.

I will provide you with an update once I hear back from the team.

Regards,

Deepak

Reply URL

Deepak Chaganti ●

Hi Stefan,

I have an update rom the team:

Unfortunately, it is not possible to leave email field as null/empty because it is still used unique identifier for the user even if we choose 'username' login instead of email.

A workaround is to switch on login by username, then set the email address to some random value that passes email validation, such as <random uuid>@a.b . This value would have to be different for each user.

Please let me know if that helps.

Thanks,

Deepak

Reply URL

Stefan Hall ●

Hi Deepak,

OK, but then the API documentation is wrong. It says: “can also be empty”.

;) Stefan

URL

Deepak Chaganti ●

Hi Stefan,

The team is currently investigating the API documentation which says it can be empty.

Please let me know if you would like this to be raised as an enhacement request or if there is anything else that I can assist you with.

Thanks,

Deepak

URL

Stefan Hall ●

Hi Deepak,

I don't understand your dependence on the email address. You do not use it at any point after the initial creation of a user. It may have been copied into the userID and the login process always runs against the userID.

But anyway, an enhacement request takes far too long for me. I now have the information and am building a technical workaround for us. It's faster and works. You can complete the thread.

;) Stefan

URL

Deepak Chaganti ●

Hi Stefan,

Thanks for letting me know that you have a workaround in place.

Sure, I will go ahead and mark this as completed.

Regards,

Deepak

URL