[PR #619] Add VigiloAuth to Awesome-Sysadmin #1235

New Issue

GiteaMirror · 2025-11-19T21:10:59-06:00

GiteaMirror commented

2025-11-19 21:10:59 -06:00

Original Pull Request: https://github.com/awesome-foss/awesome-sysadmin/pull/619

State: closed
Merged: No

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

Your additions are Free software
Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
Submit one item per pull request. This eases reviewing and speeds up inclusion.
Format your submission as follows, where Demo and Clients are optional.
Do not add a duplicate Source code link if it is the same as the main link.
Keep the short description under 80 characters and use sentence case
for it, even if the project's webpage or readme uses another capitalisation.
Demo links should only be used for interactive demos, i.e. not video demonstrations.
- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
Additions are inserted preserving alphabetical order.
Additions are not already listed at awesome-selfhosted
The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
You have searched the repository for any relevant issues or PRs, including closed ones.
Any category you are creating has the minimum requirement of 3 items.
Any software project you are adding to the list is actively maintained.
The pull request title is informative, unlike "Update README.md".
Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
"Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

Why is it awesome?

I think that it is awesome because it allows developer to have a fully customizable Identity/Auth server for their system. It also passed the OIDF Conformance tests and official certification is actively being pursued.

Have you used it? For how long?

I haven't used it in a business/professional setting since it is still a work in progress. Most OAuth flows are fully functional but it is missing an admin UI and the Device code flow.

Is this in a personal or professional setup?

At the moment it is personal, but I am hoping that it will be used in a professional setting at one point.

How many devices/users/services/... do you manage with it?

None at the moment.

Biggest pros/cons compared to other solutions?

I think that the biggest pro compared to other solutions is that almost everything’s configurable: Token lifetimes, password policies, SMTP settings, rate limits, HTTPS enforcement, auth throttling. Basically tried to make it so you don't have to fork the code just to change basic behavior. The biggest con is that it is not a mature system, it's been thoroughly tested with the compliance tests, but it hasn't been "battle tested".

Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

**Original Pull Request:** https://github.com/awesome-foss/awesome-sysadmin/pull/619 **State:** closed **Merged:** No --- Thank you for taking the time to work on a PR for Awesome-Sysadmin! To ensure your PR is dealt with swiftly please check the following: - [x] Your additions are [Free software](https://en.wikipedia.org/wiki/Free_software) - [ ] Software your are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). - [x] Submit one item per pull request. This eases reviewing and speeds up inclusion. - [x] Format your submission as follows, where `Demo` and `Clients` are optional. Do not add a duplicate `Source code` link if it is the same as the main link. Keep the short description under 80 characters and use [sentence case](https://en.wikipedia.org/wiki/Letter_case#Sentence_case) for it, even if the project's webpage or readme uses another capitalisation. `Demo` links should only be used for interactive demos, i.e. not video demonstrations. ``- [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language` `` - [ ] Additions are inserted preserving alphabetical order. - [x] Additions are not already listed at [awesome-selfhosted](https://awesome-selfhosted.net) - [x] The `Language` tag is the main **server-side** requirement for the software. Don't include frameworks or specific dialects. - [x] You have searched the repository for any relevant [issues](https://github.com/awesome-foss/awesome-sysadmin/issues) or [PRs](https://github.com/awesome-foss/awesome-sysadmin/pulls), including closed ones. - [ ] Any category you are creating has the minimum requirement of 3 items. - [x] Any software project you are adding to the list is actively maintained. - [x] The pull request title is informative, unlike "Update README.md". Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb, "Remove aaa from bbb" for removing, "Fix license for aaa", etc. -------------- Please take some time to answer the following questions as best you can:  - **Why is it awesome?** I think that it is awesome because it allows developer to have a fully customizable Identity/Auth server for their system. It also passed the OIDF Conformance tests and official certification is actively being pursued. - **Have you used it? For how long?** I haven't used it in a business/professional setting since it is still a work in progress. Most OAuth flows are fully functional but it is missing an admin UI and the Device code flow. - **Is this in a personal or professional setup?** At the moment it is personal, but I am hoping that it will be used in a professional setting at one point. - **How many devices/users/services/... do you manage with it?** None at the moment. - **Biggest pros/cons compared to other solutions?** I think that the biggest pro compared to other solutions is that almost everything’s configurable: Token lifetimes, password policies, SMTP settings, rate limits, HTTPS enforcement, auth throttling. Basically tried to make it so you don't have to fork the code just to change basic behavior. The biggest con is that it is not a mature system, it's been thoroughly tested with the compliance tests, but it hasn't been "battle tested". - **Any other comments about your use case, things you've found excellent, limitations you've encountered... ?**

GiteaMirror added the pull-request label 2025-11-19 21:10:59 -06:00

GiteaMirror closed this issue

2025-11-19 21:10:59 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sysadmin#1235