Talk:Web API security

This article is within the scope of WikiProject Computer security, a collaborative effort to improve the coverage of computer security on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer securityWikipedia:WikiProject Computer securityTemplate:WikiProject Computer securityComputer security

???

This article has not yet received a rating on Wikipedia's content assessment scale.

???

This article has not yet received a rating on the project's importance scale.

This article is supported by WikiProject Computing.

Things you can help WikiProject Computer security with:

Article alerts will be generated shortly by AAlertBot. Please allow some days for processing. More information...

Review importance and quality of existing articles
Identify categories related to Computer Security
Tag related articles
Identify articles for creation (see also: Article requests)
Identify articles for improvement
Create the Project Navigation Box including lists of adopted articles, requested articles, reviewed articles, etc.
Find editors who have shown interest in this subject and ask them to take a look here.

So happy to find that someone had written this page. Thank you! I went through and tweaked the grammar a little in the first paragraph. But as I was going through, I realized that the article is only about authentication and authorization. Since Web API security should probably include other things as well, maybe it should be called Web API Authorization and Authentication? Or maybe it should be called a stub? But it's really too thorough a treatment of Web API AuthN and AuthZ to be called a stub. Perhaps you were thinking to return and add more. That would be great!

There aren't any sources for the section on Fine-Grained authorization for APIs. I also removed the link to Axiomatics, since it gives the impression of being planted by the company, whether it was or not. Caesar's wife should be above reproach :D.

There are more grammatical issues peppered throughout the article, so it could use some further editing, but it's a great start!

At any rate, here are some things that I suggest should be added in the future (in no particular order): OpenID Connect (OIDC) (goes with the OAuth 2.0 discussion) REST Security (after briefly explaining what a REST API is and linking its page) SOAP Security (after briefly explaining what a REST API is and linking its page) TLS (instead of just SLL) Encrypting data at rest (as opposed to just in transit) Sanitizing data Logging and Monitoring Quotas and throttling API Gateways API Keys and their dangers Maybe common attacks, but definitely common weaknesses (https://owasp.org/www-project-api-security/) — Preceding unsigned comment added by Nifa2393 (talk • contribs) 06:28, 7 July 2020 (UTC)[reply]