Hi team
In our signup, we don’t use the built-in Captcha solution from Okta
Instead, we pass the captcha attribute via registration inline-hook and we validate captcha in our backend. That we do in Classic and we are moving towards OIE
Now in OIE, what I noticed is, if the captcha attribute is not listed in the User Profile Policy, we cannot send it in the userProfile payload, but that also adds the attribute to the user’s Okta profile.
Question is, how can I pass a temporary attribute in the /new registration payload in a way that is not stored but only used for a side validation?
Any help would be much appreciated
Anthony Leandro
Splunk/Cisco