Simran Khosla

Just wanted to add to the chorus that we are also currently making this call through a server side GET so -- changing this to a front end javascript post is a pretty annoying addition for us. It's doable but keeping the legacy endpoint around would be a preferable solution for us as well. 

One more question for you Charlie. 
We'd like to pass both an organization and an organization_id as part of the JWT when we login / create users. There's a few things I'm confused about -- i

1. It says if we pass an organization_id claim on the token "If both organization and organization_id are supplied, organization is ignored." -- we're looking to see how we would get both pieces of information in there. Essentially our data is structured with Org#22: Organization Name. So we'd like to pass both pieces of information over here so we can store the ID and the Organization name. How would you suggest we do this? Should we just add it to a custom user field instead and use Organization. 

2. We also have a case where users can have multiple organizations so we know we can pass strings as the organizations attribute but, is it possible to also supply a set of IDs there?

Thanks in advance for your assistance!

Hey Charlie thanks so much for your response!
I actually deleted my comment because I realized we just hadn't hit the button for Team Members to check the box to use JWT. =\ Foolish mistake on my end and all seems to be working fine now!

 But thank you for your note! I can absolutely remove expiration time to clean this up as well !