# Single Sign-On support Beta This feature is in BETA. Please reach out if you would like to use it. Wallet-as-a-Service (Palisade) now supports Single Sign-On (SSO) using a third party login. If you are using third party platforms such as Okta, JumpCloud, etc., then using Wallet-as-a-Service (Palisade) SSO support, you can continue to use your login with Wallet-as-a-Service (Palisade). **When to use SSO with Wallet-as-a-Service (Palisade)**: * You are confident in your security posture and SSO configuration * You want to keep sign-in controls consistent with your organization **When NOT to use SSO with Wallet-as-a-Service (Palisade)**: * You want to segregate both authentication and authorization from your organization's single sign-on * You are not confident your organization's SSO controls are strong enough to also protect your access to Wallet-as-a-Service (Palisade) Note that once you switch to using SSO with Wallet-as-a-Service (Palisade), it is your responsibility to secure not only your SSO access but also ensure you have adequate governance controls in place that prevent unauthorized access to Wallet-as-a-Service (Palisade). ## How to configure SSO You must have Administrator access (or equivalent) on your authentication platform that you want to configure as SSO, and Administrator role on Wallet-as-a-Service (Palisade) in order to carry out the following steps. Login to your organization on Wallet-as-a-Service (Palisade) as administrator: 1. Go to [Settings / Security](https://app.development.palisade.co/settings/security) 2. Create a new authentication method ![SSO](/assets/single_sign_on_1.b195d01fc34c4d8ee444194b9cb72c8d5ccacdc5afd1648d58bdf2d3ef6a36d1.3d0a9b10.png) 1. Follow the wizard to configure with JumpCloud or whatever SSO you are using. ![SSO](/assets/sso_2.5ebdfce555af999614b2f0e00b55d60823b1e57ffcbf7a36571328ca6889e81a.3d0a9b10.png) 1. Set the auth method to be default (this is very important, as once a user has been invited it's not possible to change the auth method). ![SSO](/assets/sso_3.75d9030e3879ac18976d8612eebec1a6e346beef7c08d0ab4a5b0ad84adad95b.3d0a9b10.png) 1. You can invite users as normal using their SSO email addresses. 2. User accepts invite as normal. 3. User can then use "Continue with SSO" to log in via SSO. ![SSO](/assets/sso_4.2425febd2d1aa6f73f1293aedba22a163914869f3928a2b74dd02d5c86abeab1.3d0a9b10.png)