Exam 350-401 topic 1 question 280 discussion

How can a public API resource be in a secure vault? It's public (!) and holds no credentials. I think it should be: Public API resource - OAuth username and passeord in an encoded string - secure vault authorization through indentity provider - HTTP basic authentication

The correct answer is: Public API resource = OAuth. OAuth is used to protect APIs, it's like when you login to a remote website with Your Google Login Creds. The remote website issues an authentication token to Google, Google authenticates you, if authenticated, allows the access request to the user request. username and password in an encoded string = HTTP basic Authentication because you can do basic username and password authentication via HTTP basic authentication because HTTP is encoded with UTF-8, ASCII, ISO-8859-1, or BASE64 for example. These are all basic HTTP methods of Encoding. Authorization through identity provider = SecureVault because SecureVault is like CyberArk, it centralizes credentials and becomes the identity provider and only allows you to log into appliances and devices after authenticating with the SecureVault (such as CyberArk).

HTTP basic authentication -username and password in an encoded string OAuth - authorization through identity provider Public API - public API resource

Please type oauth in google. It is Public API resource. Answer should be; OAuth HTTP basic authentication Secure Vault

I'm confused. What's the right answer?

OAuth is one of many solutions you can use to protect your APIs and other resources. It allows users to securely delegate access to resources without sharing their original credentials. OAuth2 has been around since 2012 as a standard and is built on lessons from other, earlier standards, including OAuth1 and SAML.

Agree with Johconnor

OAuth is a way to get access to protected data from an application. It's safer and more secure than asking users to log in with passwords., NO CORRECT , , oauth is an application