Hello team! I'm having issues with updating a pass...
# fleet
s
Hello team! I'm having issues with updating a password-login user to an sso-login. When clicking on the "Enable single sign-on" box, the password box is available but empty, so the request sends the "password" field also empty and it fails. I remember that in previous versions of Fleet, when enabling the SSO option, the password field was disabled and not sent in the request. Is there any other way to enable the SSO to this user besides using the REST API?
n
Hey Saulo, sorry you’re running into this issue. What version of Fleet are you on?
s
Hey! I've just updated to v4.17 this morning
n
Got it. This looks like a possible bug in Fleet. The Fleet team is digging into this now. Again, sorry you’re running into this.
s
No worries! I'm using the REST API as workaround. Thank you guys for the support!
k
Hey, @Saulo Guilhermino! I was able to reproduce this, but only if I click in to the password field and type and then delete. Do you have the same issue if you avoid the password field entirely when moving a user to SSO only?
s
Hello @Kathy Satterlee! My problem was that my password manager browser extension was automatically filling other users' Password field with my password. I disabled autocomplete and now it worked. Before that I was clearing the filled in password to make sure I wasn't messing up some other user's profile. In short, yes, my situation is exactly like the one you described.
k
I wondered if that might be the case. I'm glad there's a workaround for now! I'll update this thread shortly with a link to a bug report.
metal 1
s
Okay, Thank you!
Just spotted another bug: Even after a successful user update, when trying to update another user the window never stops loading until I refresh the page
k
I saw the same thing when testing and have that on my list to report as well. I'll include that link here too. Thanks for bringing it up!
s
Nice, thank you!
k
s
Great! Thanks for the support!
k
Any time! Here's that second report: https://github.com/fleetdm/fleet/issues/6595
1