Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: update Kanidm setup instruction #53

Merged
merged 4 commits into from
Jan 19, 2025

Conversation

astappiev
Copy link
Contributor

No description provided.

@astappiev astappiev changed the title Update Kanidm setup instruction Docs: update Kanidm setup instruction Jan 18, 2025
@astappiev
Copy link
Contributor Author

@sevensolutions should be fine to merge now

@sevensolutions
Copy link
Owner

LGTM. Thx for documenting this 👍.

@sevensolutions sevensolutions merged commit d80dcd1 into sevensolutions:main Jan 19, 2025
@sevensolutions sevensolutions added the backport/production Backport this PR to the production branch label Jan 19, 2025
github-actions bot pushed a commit that referenced this pull request Jan 19, 2025
* Update Kanidm setup instruction

* docs(kanidm): add tokenValidation to solve missing claims

* docs(kanidm): improve presentation

* docs(kanidm): further improve presentation

(cherry picked from commit d80dcd1)
Copy link

💚 All backports created successfully

Status Branch Result
production

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

sevensolutions pushed a commit that referenced this pull request Jan 19, 2025
* Update Kanidm setup instruction

* docs(kanidm): add tokenValidation to solve missing claims

* docs(kanidm): improve presentation

* docs(kanidm): further improve presentation

(cherry picked from commit d80dcd1)

Co-authored-by: Oleh Astappiev <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/production Backport this PR to the production branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants