With the recent Fall 2010 release of Service-now.com, a formerly optional feature called "strict SOAP security" is now turned on by default for any instance that has Basic Authentication turned on (which it is for nearly all of our instances). One consequence of this is that MID servers that authenticate to their Service-now.com instance will no longer work unless the user they're configured to log in with has the appropriate role.
Sound intimidating? It's not — we've made it almost trivially easy.
All you have to do is add a new role ("mid_server") to the MID server users. Example at left. Note that when you add the "mid_server" role, the other soap roles are added automatically.
2 Comments
