No support for `alias1..4` parameter to `update_user` about duo_client_python

[DuoKristina]

Thanks for pointing this out. We'll update update_user in the demo to include those additional fields.

[gettes]

When do you think we can see alias1-4 support??? I need to be able to search for users with their aliases and to update them. Thanks

[JamesFCoombs]

I am also waiting on this. I see that the code is complete and is just awaiting the PR to be approved, any idea when this will happen?

[gettes]

No idea. I have copied one of the sales engineers with whom I have also been working who indicated he would try and escalate to get this resolved.

…

On Sep 10, 2018, at 11:53 AM, James Coombs ***@***.***> wrote: I am also waiting on this. I see that the code is complete and is just awaiting the PR to be approved, any idea when this will happen? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#45 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWpd9n5ZsJKpa5H4K1kf-WMuRdgEqfUks5uZorzgaJpZM4TPGPS>.

[DuoKristina]

You're welcome to fork and pull that PR in for your own use.

[gettes]

Understood. We are interested in having this be something supported. The APIs are an important part of the Duo ecosystem. We understand and appreciate the language which limits Duo’s responsibility but the reality is that these APIs are at the core of being able to integrate with Duo and the success of Duo at larger organizations. Please consider having these changes included and made available and not as a one-off. I have submitted a ticket to this effect (# 00278761) Thank you. /mrg

…

On Sep 10, 2018, at 1:11 PM, Kristina Birk ***@***.***> wrote: You're welcome to fork and pull that PR in for your own use. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#45 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWpd5ARmq3sad0sbMwGGhsa1-rBo-7Uks5uZp1FgaJpZM4TPGPS>.

[BillWeiss]

Just creating an explicit link: this would be fixed by #57 , I think. As a customer, it would be rad to have this merged (or some feedback there about what it's missing).