Allow adding custom query params to custom social connection /token calls

Feature: Allow adding custom query params to custom social connection /token calls

Description: This is currently possible on /authorize calls but not /token calls

Use-case: I want to implement TikTok as a custom social connection but they require client_key to be passed on the /token call instead of client_id

Hey @dseravalli thanks for the feedback request - I’ve noticed an influx of similar topics as well as internal chatter around this of late - It’s good to get it on the board as I’m sure other community members will upvote. Our product team keeps a close eye on these for community engagement so let’s hope it garners some attention :crossed_fingers:

+1
Quite frustrating that TikTok decided to not to implement the OIDC standard “client_id”

Hey @dseravalli and @adriant !

Just wanted to follow up on this and highlight a recent blog post of ours that outlines creating a custom social connection with TikTok - In particular how to use upstream params to pass custom params during authentication:

Hope this helps!