Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/github/entitlements-app
The Ruby Gem that Powers Entitlements - GitHub's Identity and Access Management System
https://github.com/github/entitlements-app
entitlements iam security
Last synced: about 1 month ago
JSON representation
The Ruby Gem that Powers Entitlements - GitHub's Identity and Access Management System
- Host: GitHub
- URL: https://github.com/github/entitlements-app
- Owner: github
- License: mit
- Created: 2022-06-07T16:19:51.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-05-22T21:27:46.000Z (4 months ago)
- Last Synced: 2024-05-22T22:32:30.576Z (4 months ago)
- Topics: entitlements, iam, security
- Language: Ruby
- Homepage:
- Size: 13.2 MB
- Stars: 402
- Watchers: 12
- Forks: 16
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.md
- Code of conduct: CODE_OF_CONDUCT.md
- Security: SECURITY.md
Awesome Lists containing this project
README
# entitlements-app
[](https://github.com/github/entitlements-app/actions/workflows/acceptance.yml) [](https://github.com/github/entitlements-app/actions/workflows/test.yml) [](https://github.com/github/entitlements-app/actions/workflows/lint.yml) [](https://github.com/github/entitlements-app/actions/workflows/build.yml) [](https://github.com/github/entitlements-app/actions/workflows/release.yml) [](https://github.com/github/entitlements-app/actions/workflows/codeql-analysis.yml) [](https://img.shields.io/badge/coverage-100%25-success) [](https://github.com/github/rubocop-github)
`entitlements-app` is a Ruby gem which provides git-managed LDAP group configuration and access provisioning to your declared resources. It powers Entitlements, GitHub's internal Identity and Access Management (IAM) system. Entitlements is a pluggable system designed to alleviate IAM pain points.
## Quick Start
See [getting started](docs/getting-started.md) for quick start, and [entitlements-config](https://github.com/github/entitlements-config) for example configuration.
## Inputs
Entitlements currently supports a single input option of configuration files in the form of `.txt`, `.rb` and `.yaml`.
### Git-managed config
Entitlements receives input from configuration files. By using git to back the config files, every file has a complete and visible audit trail.
See [configuration](docs/configuration.md) for a complete guide on entitlements configuration.
### Populating config from a source of truth
Entitlements requires an initial Org Chart configuration to define all of the valid users available to the system.
See [orgchart](docs/orgchart.md) for a complete guide to configuring your org chart data.
## Configuration
### Metadata
Entitlements allows for metadata tags which can be used to indicate attributes of the entitlements config other than membership. These metadata tags can be used to build additional automation on top of the Entitlements system.
For examples of ways to leverage metadata tags, see [metadata](docs/metadata.md)
### Expirations
Entitlements allows for expirations at the file level and the user/group level.
See [expirations](docs/configuration.md#expiration) for more on expirations.
### Filters
Entitlements supports a concept of filters. This allows you to group employees defined in your org chart by classifications, and require explicit access definitions for those employee classifications.
For examples on filters, see [filters](docs/filters.md)
### Example
There is an example configuration repo [here](https://github.com/github/entitlements-config)
## Outputs
### LDAP
Out of the box, Entitlements will output your sets to LDAP.
See the [OpenLDAP documentation](https://www.openldap.org/doc/) for more on LDAP.
## Plugins
Entitlements is a pluggable system. Plugins can be built for additional inputs and outputs.
For more on building plugins, see [plugins](docs/plugins.md)
## Contributing
Please see [CONTRIBUTING](CONTRIBUTING.md) for details.
## Security
We take security very seriously. Please see [SECURITY](SECURITY.md) for details on how to proceed if you find a security issue.
## Release 🚀
To release a new version of this Gem, do the following:
1. Update the version number in the [`lib/version.rb`](lib/version.rb) file
2. Run `bundle install` to update the `Gemfile.lock` file with the new version
3. Commit your changes, push them to GitHub, and open a PR
Once your PR is approved and the changes are merged, a new release will be created automatically by the [`release.yml`](.github/workflows/release.yml) workflow. The latest version of the Gem will be published to the GitHub Package Registry and RubyGems.