James Shield
I have a ticket open but wanted to query the larger community as well. Is anyone else having issues where calls made from Azure won't authenticate after last weekend's update to W891A0 was rolled out?
0
Comments
Please sign in to leave a comment.
That ticket was harder to figure out that I thought it would be. From the conversation, it sounded like everything was working in the browser, but not Azure. Deeper digging - it looked like there were two OASIS user identities involved. One was setup with O4 access and the other was not.
This is a good post for others to review as the new O4 Access drop-down in the user editor controls how much web access a user has (if any at all). New users default to no access and for users logging in using a browser or device the new setting was quickly identified. API users appear to have found the error and used support to resolve - although it is a bit frustrating to figure out depending upon what is being used to call O4.
NOTE: API only users should select API access. Currently this just disables the UI elements, but will later activate more sophisticated API calls.
There will be more on security over the next few months. It's the internet...