First of all, thank you all for trying out ACUL! I am one of the product manager for this feature. Sorry for the confusion around the docs and Quickstart. We are in the process of reworking the docs and Quickstarts to better align with the current EA features and functionality. I will work with my team to get the ACUL Quickstart Doc updated to avoid confusion.
Regarding your questions, and to help clear up the confusion:
- The best place to start is the setup recommended in the sample application. This is still under active development and will change and expand quite a bit in the coming months as we near GA.
- The docs for the Management API are up to date and should work as expected for configuring Universal Login to use ACUL for a specific screen.
- @BrandenRobinson you are correct that the error you are seeing is because the root div is not included in the page. We don’t add this by default because the various JS frameworks expect different things. There is code in
main.tsx
in the sample app that shows a simple way to do this. - @jdrew1 regarding accessing the data in the Pre User Registration action… when submitting your signup form you need to prefix the custom data keys with
ulp-*
. This is using Custom Prompts under the hood to capture and forward the data.
screenProvider.signup({
email: <EMAIL_INPUT_VALUE>,
password: <PASSWORD_INPUT_VALUE>,
"ulp-first-name": <INPUT_FIELD_VALUE>
});
Note: The same thing will work on the login screens with the exception that the data will be surfaced in the Post Login action instead.
I hope that helps clear things up!