# "Full Name" Shown on /About With Full Name Option Disabled

**URL:** <https://meta.discourse.org/t/full-name-shown-on-about-with-full-name-option-disabled/50385>\
**Category:** Bug\
**Created:** [Setembro 20, 2016, 12:18pm UTC](https://meta.discourse.org/t/full-name-shown-on-about-with-full-name-option-disabled/50385 "2016-09-20T12:18:30Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Koinu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/koinu/32/120781_2.png) [@Koinu](https://meta.discourse.org/u/Koinu)\
**Post date:** [Setembro 24, 2016, 1:52pm UTC](https://meta.discourse.org/t/full-name-shown-on-about-with-full-name-option-disabled/50385/14 "2016-09-24T13:52:21Z")

</div>

Apologies for any inaccuracies—this is from memory, from over a year ago: When implementing my SSO I found that if the SSO payload omitted or left the “name” field empty, that there was some code in Discourse itself that would populate it with a value inferred from the user’s email. The workaround was to have the SSO explicitly populate the “name” field as a copy of the username.

Because names-off does not seem to be the most-tested configuration, I’d recommend a bulk sync of you users from your SSO and looking in the db table to verify that you’ve clobbered all the email-derived names, just in case there are any future bugs that leak the name field.

---

_[View the full topic](https://meta.discourse.org/t/full-name-shown-on-about-with-full-name-option-disabled/50385)._