# Switching from local user database to SAML login

**URL:** https://community.jenkins.io/t/switching-from-local-user-database-to-saml-login/1305
**Category:** Using Jenkins
**Tags:** question
**Created:** [January 21, 2022, 7:57pm UTC](https://community.jenkins.io/t/switching-from-local-user-database-to-saml-login/1305 "2022-01-21T19:57:55Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![theofficefan](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@theofficefan](https://community.jenkins.io/u/theofficefan)
#### Post date: [January 21, 2022, 7:57pm UTC](https://community.jenkins.io/t/switching-from-local-user-database-to-saml-login/1305/1 "2022-01-21T19:57:55Z")

</div>

I am currently running Jenkins 2.318 and testing SAML logins. It works, but noticed that if everything about the user is not the same (display name, case, etc), it will create a duplicate user. Is there a sure way to make sure that when I go live, the SAML login will take over the current local user? Also, is there any way to get the group attribute to pass correctly? I can’t seem to get that to work. For the record, I am using JumpCloud as the SSO provider.