title: Understanding Client in OAuth2
body: <p>I am having some difficulty understanding OAuth and some of it's terms. Specifically the idea of the <code>Client</code>. I am wondering if I might be misunderstanding the <a href="https://www.rfc-editor.org/rfc/rfc6749" rel="nofollow noreferrer">RFC 6749</a> as it relates to a <code>Client</code>.</p>
  <p>I have an of API that I would like to access via a Javascript web application (HTML and jQuery). The Javascript application will use jQuery to make AJAX calls to the API. Depending on the username/password submitted by the user of the Javascript application different API's will be available.</p>
  <p>In this context, is my Javascript application considered the <code>Client</code> by OAuth? I am confused because <a href="https://aaronparecki.com/2012/07/29/2/oauth2-simplified" rel="nofollow noreferrer">other documentation</a> I have read refers to the <code>Client</code> as <strong>the third party application</strong>, yet in my case this is not a third party application. I am not making use of third party logins (such as Google, Facebook, or Twitter). Is the <code>Client</code> that OAuth is referring only apply to third party logins?</p>