F
F
FeL1ksS2018-11-01 16:03:23
OAuth
FeL1ksS, 2018-11-01 16:03:23

How to implement one authorization service?

Hello.
There is a project on Laravel, another one will be developed. What is common between them is users (corporate), there is no registration.
You need a single point of entry through which users will log in and access other applications. You also need to issue access rights (roles) to users from one place, and not in each project separately.
Implementation:

  • Deploy another Laravel project by installing Laravel Passport, redirect to it, log in, get a token. In the same project, implement an admin panel for issuing roles

Questions:
  • How to configure other projects for this authorization method?

Install Laravel Socialite on them and write your provider? By type of authorization via github, google?
  • What to do after receiving the token?

In the Socialite implementation examples, after receiving the token, a user is created (if it does not exist) and logged in.
But then each project has its own table with users, although in fact they are the same. Is this true in my case? And how are they then given roles?
In an already existing project, the laravel-permission package is used for roles, what should we do now? Use Token Scopes?
And the main question is, am I thinking in the right direction?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
I
Ivan Shumov, 2018-11-01
@FeL1ksS

Get a ready solution. You need an Identity Server with SSO. I would recommend Auth0 or WSO2

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question