No user account after social login

I implemented OAuth1 login with Xero, by registering a custom OAuth1 connection, implementing fetchUserProfile in a way that seemed sensible. I think everything is hooked up correctly, because I am able to log in using Xero, but then I never see a User appearing on the dashboard, nor getting anything returned by Management API calls to get all users.

There seems to be a piece missing. Somebody out there who has a clue what I might be dealing with here?

![alt text][1]
![alt text][2]

Details from the Signup log message:

  "date": "2017-12-29T20:43:25.332Z",
  "type": "ss",
  "connection": "custom-xero",
  "connection_id": "con_Wn1aWdRfWYvMIDXZ",
  "client_id": "DIGRyhLdgwm5I351toM5eZksUfW1KA9K",
  "client_name": "Vue-day6",
  "ip": "",
  "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36",
  "details": {
        "name": "oauth1-authenticate",
        "initiatedAt": 1514580198654,
        "completedAt": 1514580203156,
        "timers": {},
        "connection": "custom-xero",
        "elapsedTime": 4502
        "name": "consent",
        "initiatedAt": 1514580203167,
        "completedAt": 1514580205314,
        "grantInfo": {
          "id": "5a46a8ed105d880aef300af3",
          "audience": "",
          "scope": "openid profile",
          "expiration": null
        "elapsedTime": 2147
    "initiatedAt": 1514580198033,
    "completedAt": 1514580205331,
    "elapsedTime": 7298
  "user_id": "oauth1|custom-xero|QAGIJZAPZMUWKA1SFTSBBDTMCJ6LUF",
  "user_name": "",
  "strategy": "oauth1",
  "strategy_type": "social",
  "auth0_client": {
    "name": "auth0.js",
    "version": "8.11.2"
  "log_id": "49574419589858254662358178261146763179152869192904998946"

Based on the information and logs provided what is likely happening is not related to the custom OAuth 1 connection, but more an issue with user search functionality which the dashboard makes use of so a failure in user search means no users are shown. If the tenant/domain in question was created a significant time ago, but did not show active usage the user search functionality would have been disabled as part of an incident response. The user search could then be enabled again on a case by case basis and upon request for these inactive tenants, however, at this time that ability was removed because there are plans to re-enable it for all accounts even if a request was not made; this should be coming in the next weeks.

If you’re still during development phase my recommendation would be to create a new tenant and perform the development phase there; new tenants should not be affected by the user search situation.