# Editing SSO overrides

**URL:** https://meta.discourse.org/t/editing-sso-overrides/88530
**Category:** Feature
**Created:** [5월 27, 2018, 3:39오전 UTC](https://meta.discourse.org/t/editing-sso-overrides/88530 "2018-05-27T03:39:07Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Karl\_Romanowski](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/karl_romanowski/32/87676_2.png) [@Karl\_Romanowski](https://meta.discourse.org/u/Karl_Romanowski)
#### Post date: [5월 27, 2018, 3:39오전 UTC](https://meta.discourse.org/t/editing-sso-overrides/88530/1 "2018-05-27T03:39:07Z")

</div>

When the SSO options to override username and name are set to true editing those fields in the Admin UI should be disabled. Any edits there would just be overwritten on the next login anyway.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5월 27, 2018, 3:39오전 UTC](https://meta.discourse.org/t/editing-sso-overrides/88530/2 "2018-05-27T03:39:45Z")

</div>

Shouldn’t the admin have enough knowledge to expect that to happen?

---

<div class="post-metadata">

### Author: ![Karl\_Romanowski](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/karl_romanowski/32/87676_2.png) [@Karl\_Romanowski](https://meta.discourse.org/u/Karl_Romanowski)
#### Post date: [5월 27, 2018, 3:52오전 UTC](https://meta.discourse.org/t/editing-sso-overrides/88530/3 "2018-05-27T03:52:13Z")

</div>

Yea but moderators see those too and they would be quite confused as they are likely nontechnical staff.

It’s not a critical issue, “don’t ever push those buttons” can be a part of training.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5월 27, 2018, 3:54오전 UTC](https://meta.discourse.org/t/editing-sso-overrides/88530/4 "2018-05-27T03:54:20Z")

</div>

It’s not like anything actually bad happens if they do; it’s merely overwritten later on login by the user.

---

<div class="post-metadata">

### Author: ![Karl\_Romanowski](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/karl_romanowski/32/87676_2.png) [@Karl\_Romanowski](https://meta.discourse.org/u/Karl_Romanowski)
#### Post date: [5월 27, 2018, 3:59오전 UTC](https://meta.discourse.org/t/editing-sso-overrides/88530/5 "2018-05-27T03:59:11Z")

</div>

Worst I can imagine is they change a username to something a new user legitimately owns (and will try to claim on their first SSO login)

I’ll test what happens Monday.

---

<div class="post-metadata">

### Author: ![fefrei](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fefrei/32/119538_2.png) [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [5월 28, 2018, 9:10오전 UTC](https://meta.discourse.org/t/editing-sso-overrides/88530/6 "2018-05-28T09:10:31Z")

</div>

There’s a good reason to keep these enabled: Discourse doesn’t blindly accept the username provided by SSO; if the username is invalid, it will suggest a modified one. Sometimes, this can get you into weird situations that you can only untangle by manually renaming users.
