Resetting Email Bounce List on Trial host

Hi, I have the following problem with the trial host I I use for local development:

  • My company provides me with an email address, which is what I used to sign up for the trial host and use to do most of my testing on.
  • We also have access to an aliased email address, which we use whenever we need to test any kind of workflow where I need to add new users to the app (I cannot remove my main user as that would leave me out of the Okta admin panel).
  • Due to unexpected issues, the aliased email address ended up on the email bounce list for the trial host.
  • I read the procedure to resolve this through the API ( Org Email Settings ), but it seems that for whatever reason this endpoint cannot be used from a trial host ( Okta Help Center (Lightning) ). Currently it returns a 403 E0000006 when using a Super Admin level token.
  • So, the address is permanently on the bounce list and I cannot carry out certain critical paths on my testing. It shouldn’t need be mentioned that I cannot use any other addresses that are not provided by the company.
  • My company is already paying for Okta, this only impacts my local testing.

Any way forward I can fix my trial host on the free integrator plan?

Thanks in advance.

I can confirm that I am seeing the same behavior for an Integrator Free org, where making a request to the /org/email/bounces/remove-list endpoint with a static API token issued to a Super Admin results in a 403, but the same call works against a “regular” org.

I’m going to report this internally and will let you know once I get an update about this.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

@lsandoz we have started our investigation and wanted to ask if you’re still blocked by this or if you were able to workaround this issue.

Great, thanks!

I have found a way around it by using email + addresses, fortunately our e-mail provider supports them so I’m just able to spin up new Okta accounts for a single email account, bypassing the bounce list.

1 Like

I’m glad you were able to find a solution for you. I will add that I checked internally on this and it looks like it is intended that Integrator orgs are unable to use this endpoint as a security precaution.