H
H
HoHsi2016-03-16 19:46:18
Nginx
HoHsi, 2016-03-16 19:46:18

How to make more "beautiful" authorization through Nginx?

Good afternoon!
I inherited 10 sites here, all in different technologies and languages, but they are all one big family)
There is GitLab, Wiki, Jenkins and so on.
Now all internal sites have Nginx basic authorization, or not at all. It is dreary and lazy to monitor all these visits, and I want to achieve greater security.
The idea arose, since there is not such a big load on internal resources, to put a second proxy layer between them, using the Express.js application, through which to authorize developers, and thereby not force them to enter passwords 10 times on different sites.
How adequate is this idea, and are there already ready-made analogues?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
D
Dmitry Voronkov, 2016-03-16
@DmitryVoronkov

Usually, lpdap authorization is done to all this zoo . Conveniently. got a user, gave him a password and let him go to jenkis, gitlab, etc. An employee quit, deleted his account and goodbye.

V
Vlad Zhivotnev, 2016-03-16
@inkvizitor68sl

Fasten client certificates, you will not need to enter anything.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question