For standard connections, the value of user.identity.connection is the connection.name . However, for custom oauth2 connections that are linked to a user, the value is always “oauth2”. The value of these linked connections should be the connection.name too. Steps to reproduce: Create a new user …

I did a quick test with a database user and a custom OAuth2 connection and was not able to reproduce this issue; I’m also not aware of any recent change. One thing to take in consideration is that oauth2 will indeed appear within the identities array, but associated to the provider property. More sp…

Management api problem/bug - custom connections linked to users incorrect

Get Help

cory May 23, 2017, 1:17am 2

Did someone address this? I’m now seeing connect.name in identity[n].connection. Don’t think it was my code…

Topic		Replies	Views
Linking Accounts from Two Custom Social Connections Get Help linking , custom-social-connec	1	3519	October 21, 2020
Shopify connection with dynamic shop name Get Help social-connections , custom-social-connec	2	4970	March 2, 2018
Management API Confusing Interface Around Connection Identity Get Help api , management-api	2	3733	August 26, 2019
Searching for users who are using a specific connection Get Help	2	3724	September 5, 2019
Pre-selecting custom oauth2 connection on login Get Help connections , custom-social-connections-branding	2	632	October 20, 2023

Management api problem/bug - custom connections linked to users incorrect

Related topics