Restricted Caller Access Privileges become Invalidated

[Karen16]

Hi,

We're setting up restricted caller access privs to allow inbound actions to select the appropriate HR Service for creation of HR Core Cases (and COE cases).  I've set up the restricted caller access privilege by setting the access to 'Allowed'.  The first time I did this, the next time I found it invalidated.  I reset again and tested it a few times on Friday and it seemed stable.  However, this morning (Monday) I tested and found the access was invalidated again.  Why would it become invalidated and what can I do to force the 'Allow' to stick.  I am doing this in our Dev environment and capturing the change in an update set for moving to the other environments.

Thanks,
Karen

[Ryan Dinwiddie1 · Accepted solution]

Karen, they can become invalidated whenever a change is made to an underlying table/script/code/etc that is outside HR Core Scope and allowed in. Almost any change requires the developer to re-allow that access. Usually I have a manual step to check all of those before beginning testing etc, it should be fine after changes have stopped. Once you allow them in environments past dev, you shouldn't see this issue as often. I would not recommend forcing it "stick" since its a security measure for the data protection. 

If a calling resource changes, the restricted caller access record status changes to Invalidated. An admin user or application administrator must update the status to Allowed or Denied.

Source: https://docs.servicenow.com/bundle/orlando-application-development/page/build/applications/task/set-...

[Ashutosh Munot1]

HI,

What do you mean by invalidated. 

What is your runtime access tracking?

Thanks,
Ashutosh