Update signing key document#3102
Merged
Merged
Conversation
lourens-octopus
approved these changes
Apr 16, 2026
Contributor
|
Hey @stevencl840 - did you want to merge this PR? |
Contributor
Author
|
This code is currently disabled by a feature toggle, so it describes a feature that a customer cannot use. We will be enabling the feature in cloud and self-hosted next week, and will merge the document at the same time We didn't want to confuse customers with changes that have not been rolled out yet. |
stevencl840
force-pushed
the
sjc/update-signingkeys
branch
from
69ea3af to
bf990aa
Compare
|
Pull request environment is available at https://stoctodocspr3102.z22.web.core.windows.net. You can view the ephemeral environment status in Octopus Deploy. This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity. |
stevencl840
force-pushed
the
sjc/update-signingkeys
branch
from
bf990aa to
4bf14ae
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context 🌆
We have updated Octopus Deploy to support externally hosting OIDC public keys. This allows customers who want to keep their Octopus Deploy instance on the public internet to still use OIDC. This PR updates our documentation to reflect the change
Details 🔍
I have provided a quick summary of the benefits/trade-offs of internal and external hosting of the OIDC keys. I have also provided a summary of the external key rotation procedure.
I removed the warning block because all the functions it described are now accessible via the portal. Or have I missed something?
Warning
This should only be merged after the GitHub App self-hosted feature toggle is enabled.
This PR contributes to DEVEX-13