Passing Device and Behavioral IDs to Auth0 at Login
Before your page redirects the user to the Auth0 /authorize endpoint, attach the collector's IDs as custom query parameters that start with ext-. The Action reads two of them on each login: deviceTransactionID and ubaID. Send ID references only. For the size and format limits, see Limits for ext- Parameters in the Auth0 Login Redirect[Limits for ext- Parameters in the Auth0 Login Redirect].
To pass:
Call window._bcn.snapshot() and wait for the bundle it returns. Use it rather than the individual getters: snapshot() waits until the collector has finished and its callbacks have fired, so the IDs are complete.
Read deviceTransactionID and ubaID from the bundle, and pass them as ext-deviceTransactionID and ext-ubaID in the authorization parameters of your login redirect. The following example uses auth0-spa-js:
async function login() {
const bundle = await window._bcn.snapshot();
await loginWithRedirect({
authorizationParams: {
'ext-deviceTransactionID': bundle.deviceTransactionID,
'ext-ubaID': bundle.ubaID,
}
});
}Expected result: Your /authorize request includes both ext-deviceTransactionID and ext-ubaID.
ext- parameters are a documented Auth0 feature, not a workaround. For more information, see Auth0's article Limit of “ext-” Parameters on Universal Login Page.
For the full list of login fields that Accertify's API accepts, including these IDs, see Accertify login fields reference.
Next Steps
Continue with the Action install:
- Install the Action: Installing the Accertify Account Protection Action[Installing the Accertify Account Protection Action from the Auth0 Marketplace]
See also:
Limits for ext- Parameters in the Auth0 Login Redirect[Limits for ext- Parameters in the Auth0 Login Redirect]
Auth0 Overview[Accertify Account Protection for Auth0 Overview]
Installing the Accertify Account Protection Action[Installing the Accertify Account Protection Action from the Auth0 Marketplace]