-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
website/integrations: immich: add signing algorithm #19187
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
base: main
Are you sure you want to change the base?
website/integrations: immich: add signing algorithm #19187
Conversation
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #19187 +/- ##
==========================================
- Coverage 93.37% 93.36% -0.01%
==========================================
Files 949 949
Lines 52254 52357 +103
==========================================
+ Hits 48794 48885 +91
- Misses 3460 3472 +12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
dominic-r
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's call it the exact field in the ui in the ss of linked issue, but approving for after
rissson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd rather have people select a signing key instead of changing the alg in immich.
|
Marc, don't they already do that on L37 |
|
Interesting, then it should be sufficient I think? |
Fixed. I copied the name from their docs which seem to be outdated.
My thinking too |
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
authentik PR Installation instructions Instructions for docker-composeAdd the following block to your AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-4bdc05ca531448534dd8068b3d59342a75b46c52
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)sAfterwards, run the upgrade commands from the latest release notes. Instructions for KubernetesAdd the following block to your authentik:
outposts:
container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
global:
image:
repository: ghcr.io/goauthentik/dev-server
tag: gh-4bdc05ca531448534dd8068b3d59342a75b46c52Afterwards, run the upgrade commands from the latest release notes. |
rissson
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, after re-checking the current documentation is correct. The reporting issue is incorrect, they probably didn't select a signing key.
|
I figured about the same. Let's wait for the linked issue to respond and close this as needed |


Details
Closes #19178
Checklist
If applicable
make docs)