chore: Apply OCI source label to Docker image
This patch adds the `org.opencontainers.image.source` label to
the Zitadel Docker image. This label is used by dependency update
tools like Dependabot and Renovate to look up release notes for
Docker image updates.
Co-authored-by: Elio Bischof <elio@zitadel.com>
* docs: add instance not found troubleshoot to self-hosting
* docs: add instance not found troubleshoot to self-hosting
* docs: fix links
* docs: remove instance not found from support troubleshoot
* docs: add instance not found note on all deploy guides
* Modifying docs to comply with Google style guide for docs.
* Removed typo.
* Added FE and BE integration with ZITADEL
* Added FE and BE integration with ZITADEL
* Added FE and BE integration with ZITADEL
* Update docs/docs/guides/solution-scenarios/frontend-calling-backend-API.mdx
Co-authored-by: mffap <mpa@zitadel.com>
* Update docs/docs/guides/solution-scenarios/frontend-calling-backend-API.mdx
Co-authored-by: mffap <mpa@zitadel.com>
* Addressed @mffap's question on the PR.
* Added docs for detailed explanations for token introspection.
* Update docs/docs/guides/integrate/token-introspection/basic-auth.mdx
Co-authored-by: Fabi <fabienne@zitadel.com>
* Update docs/sidebars.js
Co-authored-by: Fabi <fabienne@zitadel.com>
* Update docs/docs/guides/integrate/token-introspection/private-key-jwt.mdx
* Addressed @hifabienne's review comments.
* Addressed @hifabienne's review comments.
---------
Co-authored-by: Dakshitha Ratnayake <dakshitharatnayake@Dakshithas-MacBook-Pro-2.local>
Co-authored-by: mffap <mpa@zitadel.com>
Co-authored-by: Fabi <fabienne@zitadel.com>
* Modifying docs to comply with Google style guide for docs.
* Removed typo.
* Added FE and BE integration with ZITADEL
* Added FE and BE integration with ZITADEL
* Added FE and BE integration with ZITADEL
* Update docs/docs/guides/solution-scenarios/frontend-calling-backend-API.mdx
Co-authored-by: mffap <mpa@zitadel.com>
* Update docs/docs/guides/solution-scenarios/frontend-calling-backend-API.mdx
Co-authored-by: mffap <mpa@zitadel.com>
* Addressed @mffap's question on the PR.
---------
Co-authored-by: Dakshitha Ratnayake <dakshitharatnayake@Dakshithas-MacBook-Pro-2.local>
Co-authored-by: mffap <mpa@zitadel.com>
This fix provides a possibility to pass a domain on the session, which
will be used (as rpID) to create a passkey / u2f assertion and
attestation. This is useful in cases where the login UI is served under
a different domain / origin than the ZITADEL API.
This change renames the v2 user OTP registration endpoints and objects
to TOTP.
Also the v2 related code paths have been renamed to TOTP.
This change was discussed during the sprint review.
### Definition of Ready
- [ ] I am happy with the code
- [ ] Short description of the feature/issue is added in the pr
description
- [ ] PR is linked to the corresponding user story
- [ ] Acceptance criteria are met
- [ ] All open todos and follow ups are defined in a new ticket and
justified
- [ ] Deviations from the acceptance criteria and design are agreed with
the PO and documented.
- [ ] No debug or dead code
- [ ] My code has no repetitions
- [ ] Critical parts are tested automatically
- [ ] Where possible E2E tests are implemented
- [ ] Documentation/examples are up-to-date
- [ ] All non-functional requirements are met
- [ ] Functionality of the acceptance criteria is checked manually on
the dev system.
* feat: add fontname package and draft
* feat: change back delete visibility
* feat: replace fontname lib with opentype.js
* feat: dynamic font preview also for font name
---------
Co-authored-by: Max Peintner <max@caos.ch>
* docs: add guide for implementing ui with the new user/session api
* docs: add guide for implementing ui with the new user/session api
* docs: add oidc flow to login ui guide
This change renames the v2 user OTP registration endpoints and objects
to TOTP.
Also the v2 related code paths have been renamed to TOTP.
This change was discussed during the sprint review.
* feat(api): add password reset and change to user service
* integration tests
* invalidate password check after password change
* handle notification type
* fix proto
### Definition of Ready
- [ ] I am happy with the code
- [ ] Short description of the feature/issue is added in the pr
description
- [ ] PR is linked to the corresponding user story
- [ ] Acceptance criteria are met
- [ ] All open todos and follow ups are defined in a new ticket and
justified
- [ ] Deviations from the acceptance criteria and design are agreed with
the PO and documented.
- [ ] No debug or dead code
- [ ] My code has no repetitions
- [ ] Critical parts are tested automatically
- [ ] Where possible E2E tests are implemented
- [ ] Documentation/examples are up-to-date
- [ ] All non-functional requirements are met
- [ ] Functionality of the acceptance criteria is checked manually on
the dev system.
* fix: nil pointer on create instance add machine
* fix: instance setup with machine user pat
* fix: correct logic to write pat and key from setup without configurable scope
---------
Co-authored-by: Livio Spring <livio.a@gmail.com>
