posted on October 3, 2024

The new OAuth 2.0 option in the web service connections is really cool to reduce having to run a separate rule just to authenticate and allow us to run the rules we want to use directly. It works great with 3rd party APIs which often use a secret to login but this morning we were using it with the LF On-Prem API (which uses basic authentication to login) and having trouble.

We already have an older rule that gets the bearer token and it is working using the old basic config. 

But when we try using the automatic OAuth 2.0 config and configure the exact same body fields it says Unauthorized

0 0