Conversation
gadomski
pushed a commit
that referenced
this pull request
Apr 8, 2026
🤖 I have created a release *beep* *boop* --- ## [1.4.0](v1.3.4...v1.4.0) (2026-04-08) ### Features * build-time oidc configuration ([#380](#380)) ([12f1864](12f1864)), closes [#373](#373) ### Reverts * remove plausible analytics snippet ([#353](#353)) ([d11857e](d11857e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: ds-release-bot[bot] <116609932+ds-release-bot[bot]@users.noreply.github.com>
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
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.
I don't think there's too many cases where someone will want to configure the OIDC authority and client ID at "runtime", so for now I'm only supporting the white-label case. E.g. this would enable any client to deploy their own version of stac-map pointed at their auth provider.
This makes sense to me b/c the OIDC stuff only works if you've configured your client id and redirect URL properly, so it's a deploy-time thing.
Closes #373