Implement OAuth2 authentication for API endpoints related to code components

balintbrews → credited penyaskito → .

My experience working with setting up oauth for Entity Share was not pleasant. I've written exhaustive docs for dealing with all the various error codes you can get. Despite setting it up multiple times for several sites in a distributed network of sites sharing content I still need to consult the docs and error codes every time. So I'd be pretty keen to see if we could implement another process here? If we have a cli here can't we prompt for a username and password, hit the user.login.http route and get a cookie then just use that to make further requests to the API? This would avoid us having to add another dependency.

I completely get the appeal of avoiding the complexity, but we will need to provide OAuth2 to follow industry standards, and to account for the use case when someone wants to manage components on multiple sites.