<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5KZ00000kq1v10AAOkta Classic EngineAdministrationAnswered2025-05-01T19:20:00.000Z2025-04-30T13:51:14.000Z2025-05-01T19:20:00.000Z

ArafatH.04762 (Customer) asked a question.

Getting okta error "role: This field cannot be left blank"

Hi All,

 

Getting this error whenever I try to provision some users to pagerduty. Unsure why this error is occurring but would like some assistance on getting this person that access in okta. Thanks!

/help/servlet/rtaImage?refid=0EMKZ000000FmsZ


  • ArafatH.04762 (Customer)

    Hi @User1646066528187443648 (Okta)​ thanks for getting back to me. I was able to resync the api for pagerduty in Okta which allowed "roles" to show up when provisioning accounts which is good. But it doesn't give a dropdown of options for the roles, I have to manually type in the role based on my memory of options. How do I get that dropdown back?

  • @ArafatH.04762 (Customer)​ - when you assign a user to pager duty app , are you not seeing the role with options (in the drop down)..i.e App_>Pager Duty> Assignments-> People

  • @ArafatH.04762 (Customer)​ 

    could you try couple of things

     

    1) Application->Application and on menu loptions you should see a "More" and just select dropdown and refresh application . After this let me know if you see any difference

    2) If you assign iot to group (instead of person) does it make any difference? If you already assigned to group , if possible redo that

    3) you said you did a sync.. i am assuming you didnt create a new API Key and if you did, this API key has full access on Pagerduty side correct?

     

    If these still dosent work, i suggest you open a support ticket. Please post the result here so one of us can respond as well

     

    Thanks

    -Bala

    Expand Post
    • ArafatH.04762 (Customer)

      Hi @User1646066528187443648 (Okta)​ I've tried the first two options and it didn't seem to make a difference. As far as the API key goes it's not a new key, it's the same key as before, I simply ran the test to confirm if it's still valid and okta approved it, afterwards the "User Role" attribute came back but it doesn't have the drop down menu.

  • Hi @ArafatH.04762 (Customer)​ 

    From above what i am inferring is that your sync fixed something and broke role showing up in dropdown.

    If that is the case, can you create a new connection (with a different name) and use the same API key and see if shows role in dropdown... I am hoping this is a dev/test environment where you are trying this out?

    -Bala

    Expand Post
  • ArafatH.04762 (Customer)

    Hi @User1646066528187443648 (Okta)​ would there be a way to make a mirror (sandbox) of my company's current Okta instance? I'm the main admin for Okta so if there's anything I need to do to make it happen I'm open to that option but I'd like to try the sandbox to test that out that you mentioned. Thank you again for your help by the way.

This question is closed.
Loading
Getting okta error "role: This field cannot be left blank"