Closed tgoodsell-tempus closed 2 years ago
Added a full response example in here, mainly for my own tracking
Hi, @tgoodsell-tempus! Thanks for submitting this issue! I'll try to find a team responsible for this functionality, maybe the can give more context of what is going on.
@bogdanprodan-okta, I'll close this as I got resolution from Okta support, this was related to a hidden feature flag for self-service registration.
Specifically:
This is happening due to a prerequisite of feature flags that are mandatory for self-service registration that links the login with the email so it causes this constraint. The only solution is to either disable the self-service registration functionality or simply use different email addresses for each account.
In my case, the self-service registration
page had already been showing as disabled, so I had to have the support team disable the other flags for me.
Describe the bug?
I believe this is primarily an API bug, however since I'm using the
golang
sdk for this I'll also paste this here while I work on a support case of my own.When I attempt to create a user in Okta where I'm setting a different
email
value from thelogon
value, it's clear that is not being accepted correctly upstream. The actual "error" I'm receiving is a duplicate user entry failure, when I set theemail
to an account which already has a Okta account with that value as alogin
, while mylogin
is something which does not exist.What is expected to happen?
I'm going to paste the raw http request value from the SDK instead of the objects, since this shows the issue most clearly.
With the following create user request:
I would expect that to be a successful user create, since the
login
value does not exist andemail
does not haveValue must be unique for each user
checked in the Okta profile.What is the actual behavior?
This fails with the following error return from the API (this is the error value output in golang):
Full response example:
Based on my request above, it's clearly interpreting the
email
value as thelogin
value, which is unexpected behavior and not documented in the API docs.Reproduction Steps?
Attempt to create a new user using the API, where the
email
value matches a user who currently exists.Additional Information?
No response
Golang Version
go version go1.17.6 darwin/arm64
SDK Version
github.com/okta/okta-sdk-golang/v2 v2.9.2
OS version
No response