Aydin Mercan
e0173496c6
I think that API key generation and revocation should be done by calling the binary. Also, nuking all keys should be accessible. Public identity regeneration can use `init` again for now. I am thinking about seperating between confidential and public clients in the structure that keeps track of them. The map keeping track of the confidential should use the client base url as well. Expecting to overhaul how its done after checking RFC 8725 and other JOSE damage reduction strategies more throughly. (ugh) |
||
|---|---|---|
| .cargo | ||
| .github/workflows | ||
| doc | ||
| src | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
| schema.sql | ||
README.md
ChibiAuth
Naive OpenID Provider.
Documentation
Relevant info for development is inside the doc folder.
For administration and usage, a reference handbook will be provided in the future.
Usage
chibiauth run --database=/path/to/database/of/chibiauth.db --port 9909 --base-url 'https://example.com'
- ChibiAuth will bind to localhost, bring your own TLS terminator.
- The database is just a SQLite file, feel free to use something like litestream.
License
This repository is licensed under the EUPL-1.2. An English copy of the license text is available under LICENSE.