-2

I was looking at this documentation.

https://laravel.com/docs/5.6/passport

it is quite long and I asked myself, why would one use this, over just a normal login where you store necessary information in the session?

E.g. when to use proper API, and when to just use web form login in a normal way?

  • someone mind to explain whats wrong with the question? – Toskan Jun 11 '18 at 21:02
  • A "proper API" would allow you to share the same authentication mechanism between your web application and, say, microservices. – Robert Harvey Jun 11 '18 at 21:44
  • 1
    The linked APIs support OAuth authentication, so it seems like the question is less about API vs session state than about the uses/advantages of using OAuth. The main advantage of OAuth being that a user can authorise a third-party application to access data from their account without their actual password ever passing through that application. – Sean Burton Jun 12 '18 at 10:43
  • @SeanBurton put it as answer please, now makes sense to me – Toskan Jun 13 '18 at 4:06
1

The linked APIs support OAuth authentication, so it seems like the question is less about API vs session state than about the uses/advantages of using OAuth. The main advantage of OAuth being that a user can authorise a third-party application to access data from their account without their actual password ever passing through that application.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.