[release/8.0] Default to browser token auth in dashboard standalone #3469
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.
Backports #3427
Customer Impact
This PR changes the dashboard to default frontend auth to browser token. Previously, the dashboard would throw an error if no auth was configured unless suppressed. Providing a good default instead of an error makes using the standalone dashboard a nicer experience when getting started and it offers a secure default rather than forcing users to explicitly opt-out of auth altogether.
While making these changes, I tested the standalone dashboard much more heavily than before and found some related bugs. They're also fixed in this PR.
This PR:
Demo:
Testing
Manual and unit tests.
Risk
Low-Medium. Changing the default auth mode is a simple change. There is some new UI (message bar) for warning about unsecured OTLP endpoint.
Regression?
No
Microsoft Reviewers: Open in CodeFlow