You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4db8f3e23e
The OIDC implementation merged in #491 is flawed for multiple reasons. It assumes that the access_token returned by the IDP has to be a JWT parseable by the RP which is not the case [1]. Many major IDPs do issue tokens which are not JWTs and RPs should not rely on the contents of these at all. The only signed token which has a standardized format for direct RP consumption is the OIDC ID token (id_token), but this by default doesn't contain many claims, especially role claims are omitted from them by default for size reasons. To get these additional claims into the ID token, one needs an IDP with support for the "claims" parameter. It requires manual specification of the JWKS URL which is mandatory in any OIDC discovery document and thus never needs to be manually specified. It also makes the questionable decision to use a client-side code flow with PKCE where a normal code flow would be much more appropriate as all user data is processed in the backend which can securely hold a client secret (confidential client). This has far wider IDP support and doesn't require working with ID tokens and claim parameters. By using a server-side code flow we can also offload most complexity to the server alone, no longer requiring an additional OIDC library on the web client. Also silent logout doesn't work on most IDPs for security reasons, one needs to actually redirect the user over to the IDP, which then prompts them once more if they actually want to log out. This implementation should work with any OIDC-compliant IDP and even OAuth 2.0-only IDPs as long as they serve and OIDC discovery document. [1] https://www.rfc-editor.org/rfc/rfc6749#section-5.1 |
2 years ago | |
|---|---|---|
| .github | 2 years ago | |
| .husky | 4 years ago | |
| .vscode | 3 years ago | |
| charts/planka | 2 years ago | |
| client | 2 years ago | |
| server | 2 years ago | |
| .dockerignore | 3 years ago | |
| .gitattributes | 6 years ago | |
| .gitignore | 3 years ago | |
| CODE_OF_CONDUCT.md | 6 years ago | |
| CONTRIBUTING.md | 4 years ago | |
| Dockerfile | 2 years ago | |
| Dockerfile.base | 3 years ago | |
| LICENSE | 3 years ago | |
| README.md | 2 years ago | |
| SECURITY.md | 3 years ago | |
| demo.gif | 6 years ago | |
| docker-backup.sh | 3 years ago | |
| docker-compose-dev.yml | 6 years ago | |
| docker-compose.yml | 2 years ago | |
| docker-restore.sh | 3 years ago | |
| package-lock.json | 2 years ago | |
| package.json | 2 years ago | |
| start.sh | 3 years ago | |
README.md
Planka
Elegant open source project tracking
Client demo (without server features).
Features
- Create projects, boards, lists, cards, labels and tasks
- Add card members, track time, set a due date, add attachments, write comments
- Markdown support in a card description and comment
- Filter by members and labels
- Customize project background
- Real-time updates
- User notifications
- Internationalization
How to deploy Planka
There are 2 types of installation:
For configuration, please see the configuration section.
Contact
- If you want to get a hosted version of Planka, you can contact us via email contact@planka.cloud
- For any security issues, please do not create a public issue on GitHub, instead please write to security@planka.cloud
We do NOT offer any public support via email, please use GitHub.
Development
See the development section.
Tech stack
- React, Redux, Redux-Saga, Redux-ORM, Semantic UI React, react-beautiful-dnd
- Sails.js, Knex.js
- PostgreSQL
License
Planka is AGPL-3.0 licensed.