0D51Y00009hLcXiSAKOkta Classic EngineAdministrationAnswered2024-04-16T12:21:30.000Z2020-10-14T18:28:11.000Z2021-03-22T20:22:02.000Z

3ug5u (3ug5u) asked a question.

L10N_ERROR[event.dispatchError] Unable to remove custom profile attribute for my app

Hi all,

I wanted to fetch attribute from my user profile on my app that I created in the Okta management console. As I was testing and trying something, I added a profile attribute "customerAccointId" in both the default "User" and my Simple App "Simple *** User" by clicking and going in to "Profile".

Image is not available

And here comes the problem, in my app "Simple *** App", it turned out I did not need the newly added "customerAccountId". So I tried to remove it by clicking on the "X" button and delete it. But there was an error popped up (shown below).

Image is not available

Image is not available

Plus, I wasn't able to change the setting of my newly added, custom profile attribute, e.g. Scope and Mutability. Is this by-design or there's a way around? (given my current situation where I couldn't delete


  • User15807855251883082608 (Tier 2 - US East)

    This error is usually caused by the custom attribute has been marked as required under Directory> Self-Service Registration and afterwards also marked as required under Directory> Profile Editor, in the Okta User profile.

     

    In order to delete the attribute from the Okta User profile, go to Directory> Self-Service Registration, click the Edit button, locate the attribute in question under the Registration Form section and uncheck the "Required" box. Afterwards, go to Directory> Profile Editor, click on Okta User profile (and then after click on your App's profile), locate the attribute in the list and try removing it again.

     

    Note: In case the attribute has not been marked as required under Self-Service Registration, proceed to temporarily disabling Self-Service Registration and retry deleting the attribute from Profile Editor.

    Expand Post
  • OliverB.97049 (Isambard)

    Hi Thomas, I am also experiencing this problem. It seems to be a bug. In my case, the attribute is not marked as required (either in Self-service Registration or in Profile editor). Do you have any other suggestions?

This question is closed.

Recommended content

No recommended content found...