When you create an Authentication Factor using the /admin/v1/AuthenticationFactor API (for example, via Postman), you specify a custom authFactorId in the request payload. However, you observe that the created Authentication Factor ignores your specified ID and instead assigns a randomly generated ID. This behavior is inconsistent with other resources, such as application creation, where specified IDs are honored.
This is a confirmed product limitation. The API currently enforces a constraint that prevents the manual assignment of an ID during the creation of an Authentication Factor.
This issue is targeted to be fixed in release 4.1.1.
Until this release is available, the system continues to generate random IDs for all new Authentication Factors.