Why hide the access token from the User Agent? (OAuth Authorization Code Grant)

My understanding is that the OAuth Authorization Code Flow is used to avoid exposing the access token from the User Agent. But why?
I was reading this article (Common OAuth Vulnerabilities) by Doyensec.
It says that the Authorization Code … Continue reading Why hide the access token from the User Agent? (OAuth Authorization Code Grant)

I’m calling the API of a third party, and have to pass the credentials as parameters in a HTTPS URL. Is that safe?

Basically I am doing a GET on this URL from SAP:
https://www.thirdparty.be/webservices.php?m=get_private_information&o=json&u=username&p=password

The third party webservice does use IP-whitelisting, and they have whitelisted o… Continue reading I’m calling the API of a third party, and have to pass the credentials as parameters in a HTTPS URL. Is that safe?

I’m calling the API of a third party, and have to pass the credentials as parameters in a HTTPS URL. Is that safe?

Basically I am doing a GET on this URL from SAP:
https://www.thirdparty.be/webservices.php?m=get_private_information&o=json&u=username&p=password

The third party webservice does use IP-whitelisting, and they have whitelisted o… Continue reading I’m calling the API of a third party, and have to pass the credentials as parameters in a HTTPS URL. Is that safe?

Device Code Phishing

This isn’t new, but it’s increasingly popular:

The technique is known as device code phishing. It exploits “device code flow,” a form of authentication formalized in the industry-wide OAuth standard. Authentication through device code flow is designed for logging printers, smart TVs, and similar devices into accounts. These devices typically don’t support browsers, making it difficult to sign in using more standard forms of authentication, such as entering user names, passwords, and two-factor mechanisms.

Rather than authenticating the user directly, the input-constrained device displays an alphabetic or alphanumeric device code along with a link associated with the user account. The user opens the link on a computer or other device that’s easier to sign in with and enters the code. The remote server then sends a token to the input-constrained device that logs it into the account…

Continue reading Device Code Phishing