Skip to content

Conversation

@keithhubner
Copy link
Contributor

🎟️ Tracking

Change is coming from a customer ticket where they state that if a value is set for the push relay URL when in an air gapped environment:
"I managed to resolve problem by updating record in ConfigMap manually, however that doesn’t seem to be a good solution, since it will be changed on the next Helm upgrade.
Without it, all new user enrollments time out with following error:


=> SpanId:1a7223b33e81c28a, TraceId:9e2ded3330d58722549d9251a81d93aa, ParentId:0000000000000000 => ConnectionId:0HN9H8O6I0TVA => RequestPath:/identity/connect/token RequestId:0HN9H8O6I0TVA:00000004 => IpAddress:10.42.202.150 UserAgent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 DeviceType:9 Origin:9 ClientVersion:2024.12.0
Unable to send POST request to https://push.bitwarden.com/push/register because an access token was unable to be obtained

Would you please provide solution to update following record in ConfigMap through Helm values:

globalSettings__pushRelayBaseUri: "https://push.bitwarden.com/push/register"

globalSettings__pushRelayBaseUri: ""

📔 Objective

Allow update to the values file to specify a blank string for the globalSettings__pushRelayBaseUri env var

📸 Screenshots

⏰ Reminders before review

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

@github-actions
Copy link
Contributor

github-actions bot commented Jan 15, 2025

Logo
Checkmarx One – Scan Summary & Details5343a610-e4fe-43eb-a917-5e9ab9d490dc

Great job, no security vulnerabilities found in this Pull Request

@keithhubner
Copy link
Contributor Author

Please can we try this again?

@sonarqubecloud
Copy link

@sonarqubecloud
Copy link

sonarqubecloud bot commented Apr 9, 2025

Copy link
Collaborator

@mimartin12 mimartin12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@keithhubner CI is passing now, LGTM 🚀

@mimartin12 mimartin12 requested a review from a team as a code owner June 12, 2025 21:11
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants