By looking at the user object coming back in the api, I saw data_full_name, which worked correctly when sending it through as full_name with the SSO JWT, even though it isn't listed as one of the available properties.
https://sleekplan.com/docs/single-sign-on/#_2-generate-a-token-on-your-server