@dan Oh I see. The error in the response says:

"because it was missing a unique id in the [user.id] or enough information to store in FusionAuth (i.e. an email or username)"

In other words, "either Id or email" is missing from your request. Which makes boolean sense when thinking about it carefully.

But when first reading it, I though it meant "you need either Id or email", which is very different. I supplied one of those. I though that was what the "or" meant.

This error could be better as:

"because it was missing a unique id in the [user.id] or enough information to store in FusionAuth (i.e. an email or username). Both are necessary"

I think this might be a bug.

I made a web service for a Connector that returned:

return response.status(200).json({
    user: {
        'id': '647978c5-01a0-49b8-8f4f-daab25e7ce63',
        'password': 'password',
        'active': true
    }
});

FusionAuth System Event Log said I hadn't given it a unique id, which is not true:

Generic Connector Debug Log for [Test] with Id [b9a215ed-3078-4339-9638-62416fd20837].

3/20/2024 01:58:58 PM Z Attempting authentication request to application with Id [e9fdb985-9173-4e01-9d73-ac2d60d1dc8e] from IP address [172.27.0.1] for [myemailaddress+frontegguserc@simplelogin.com] against the URL [http://host.docker.internal:6252].
3/20/2024 01:59:00 PM Z Endpoint returned status code [200].
3/20/2024 01:59:00 PM Z Connector User:
{
  "active" : true,
  "connectorId" : "e3306678-a53a-4964-9040-1c96f36dda72",
  "data" : {
    "hi" : "hi!"
  },
  "id" : "647978c5-01a0-49b8-8f4f-daab25e7ce63",
  "memberships" : [ ],
  "passwordChangeRequired" : false,
  "preferredLanguages" : [ ],
  "registrations" : [ ],
  "twoFactor" : {
    "methods" : [ ],
    "recoveryCodes" : [ ]
  },
  "usernameStatus" : "ACTIVE",
  "verified" : false
}
3/20/2024 01:59:00 PM Z 
. WARNING DISCARDING USER Connector because it was missing a unique id in the [user.id] or enough information to store in FusionAuth (i.e. an email or username).

If I changed my service to instead return the below, the Connector works and logs me in.

return response.status(200).json({
    user: {
        'id': '647978c5-01a0-49b8-8f4f-daab25e7ce63',
        'password': 'password',
        'active': true,
        'email': email,
        'username': email
    }
});

Either a Connector should work with only a UUID, or the code and docs should change to say it requires email and username too.

@mark-robustelli Oh ok, I'll set the password to a UUID then and set the user to change password on login. I'll try on Monday. Thanks for the forum link.

I'm trying to import users without a password hash from Frontegg using importUsers in the TypeScript SDK.

Although the importusers documentation, https://fusionauth.io/docs/apis/users#request-6, says only a username and email is required, the code is telling me You must specify the [user.password] property for each user.

I've set passwordChangeRequired to true. I see some of the other user API methods have sendSetPasswordEmail, but this isn't available on the import method.

Is there a setting I can change to allow import with no password? Or must I use another method? Or is this a bug? I don't think any of the other migration tutorials we've written haven't had password hashes available.

Thanks.

@alex-patterson Thanks, this works. I thought the uuid would be better in case I ever change the role name though.

I'm creating a Role for the default Application like so, and then trying to import a user:

import {FusionAuthClient} from '@fusionauth/typescript-client';

const applicationId = 'e9fdb985-9173-4e01-9d73-ac2d60d1dc8e';
const subscriberRoleId = '635ef5c8-54c5-4605-ba0f-add6ad1578ce';
const apiKey = '33052c8a-c283-4e96-9d2a-eb1215c69f8f-not-for-prod';
const fusionauthUrl = 'http://localhost:9011';
const fa = new FusionAuthClient(apiKey, fusionauthUrl);

await fa.createApplicationRole(applicationId, subscriberRoleId, { role: {
    id: subscriberRoleId,
    isDefault: false,
    isSuperRole: false,
    name: 'Subscriber',
    description: 'Subscriber'
} });

const importRequest = { users: [user], validateDbConstraints: true };
const result = await fa.importUsers(importRequest);

Importing without user Registrations works fine, but as soon as I add a Registration, I get this error:

fieldErrors: {
      'user.registrations.roles': [
        {
          code: '[invalid]user.registrations.roles',
          message: 'Invalid Application role(s) [635ef5c8-54c5-4605-ba0f-add6ad1578ce (app: ExampleNodeApp)].'
        }
      ]
    },
    generalErrors: []

Here is the user I'm importing in JSON:

{"email":"a@example.com",
"encryptionScheme":"example-wordpress-phpass",
"factor":8,"password":"JFAkQi9rQ3pUTURWN2NjQ2xhUlNoSlB6OHN1V1FkS2M1Lw==",
"salt":"JFAkQi9rQ3pUTURWN2NjQ2xhUlNoSlB6OHN1V1FkS2M1Lw==",
"uniqueUsername":"a",
"username":"a",
"verified":false,
"active":true,
"registrations":[{"applicationId":"e9fdb985-9173-4e01-9d73-ac2d60d1dc8e","roles":["635ef5c8-54c5-4605-ba0f-add6ad1578ce"]}],
"data":{"WordPress_ID":2,"WordPress_user_nicename":"a","WordPress_user_registered":"2024-02-21 10:52:53","WordPress_display_name":"a","WordPress_nickname":"a","WordPress_wp_capabilities":{"subscriber":true},"WordPress_default_password_nag":"1"}}

What must I change in my import user to get this to work please? The applicationId is correct and the roleId, I've checked in the web interface.