MaxG.39730 (Customer) asked a question.
Where to define Registration Inline Hook Profile Data?
The Registration inline hook reference (https://developer.okta.com/docs/reference/registration-hook/) makes mention of "other custom attributes on the Sign-In Widget" in the data.userProfile section of the JSON.
I'm having trouble getting other attributes to appear in this part of the JSON. I can only ever get firstName, lastName, email and login.
Is there another place to define what appears in that profile section or is there some other way to define the profile enrollment attributes to make them appear in that JSON payload?
@MaxG.39730 (Customer) -- You have posted specifically to the Okta Workflows product sub forum. The widget (default or custom) is outside the scope of this product.
I am not an expert with Inline Hooks. However, from looking at the documentation in the section you mentioned it is indicating Okta's 4 built-in required attributes on a user profile + (any other attributes you have custom created that are also likely required to have inputs for a registration)
Inline & event Event Hooks are essentially monitoring for a specific transaction(event) occurrence then are performing an action. The difference between the two is Event Hooks just deliver a payload and the session is completed while Inline hooks deliver a payload and expect a response back.
In both instances the delivered payload is going to be the data available. If you are not seeing expected data delivered the issue is likely upstream of the "event trigger" in this case the widget (likely the submission of the payload from the widget).
If this is the Default sign-in widget you are likely better off asking your question in the Administration subforum. If this is a custom widget you may want to inquire on the developer forum.
https://devforum.okta.com
Thanks Tim. I'll re-ask this question in the other area as you've mentioned.
Hello @MaxG.39730 (Customer) Thank you for reacting out to our Community!
As per our documentation below:
"If you want to add new profile attributes, click Configure the Okta user profile to add them to the Okta user profile. They’re then available in the list on this page. Set the User permission dropdown menu to Read - Write to ensure your users can modify the new attributes after registration."
https://developer.okta.com/docs/guides/archive-set-up-self-service-registration/main/#enable-and-configure-a-self-service-registration-policy
Community members help others by clicking Like or Select as Best on responses. Try it today.
Earn Today: New Okta Community Badges Have Arrived
Hi Paul, I'm not having trouble with the self-service form itself. We have additional custom attributes being shown and filled in as expected. The problem is that data isn't in the JSON for data.userProfile for a registration inline hook. I need some of the custom data for the inline hook custom code in my API.
Do these attributes have any values? Keep in mind that if the attribute does not have any value it will not show in the API call.
I realize now that I was using the wrong property name. I was also being confused by the fact that the preview was only ever showing the 4 properties, even though the others were being sent as expected.