Skip to content
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

Add DeviceTrust badge when session upgraded #41029

Merged
merged 1 commit into from
Apr 30, 2024
Merged

Conversation

avatus
Copy link
Contributor

@avatus avatus commented Apr 29, 2024

This PR will add a badge if the webSession has been upgraded with Device Trust.

This updates our status check to include a new field, hasDeviceExtensions which returns true if the certificate for the websession have been extended with device trust extensions. In order to not have to "wait" for the first status check, I've changed the initial validateCookieAndSession to just be fetchStatus. For some reason, we did a bare validateCookieAndSession and then called it again in fetchStatus every time after.

If the session is valid, the shield icon will appear (with a hover text shown in screenshot)
Screenshot 2024-04-29 at 5 19 02 PM

Copy link

The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with changelog: followed by the changelog entries for the PR.

@avatus avatus removed the request for review from gzdunek April 29, 2024 23:13
@avatus avatus added the no-changelog Indicates that a PR does not require a changelog entry label Apr 29, 2024
@avatus avatus force-pushed the avatus/device_badge branch from 85e9be3 to ec09f25 Compare April 29, 2024 23:22
@avatus
Copy link
Contributor Author

avatus commented Apr 30, 2024

@kimlisa updated and reverted the fetchStatus change. Because updating the session after the initial load wouldn't really do anythng, I've just removed any changes to fetchStatus at all. We only care about checking the deviceExtensions on initial validation now and thats it. this can be expanded upon later if necessary but good enough for now

@public-teleport-github-review-bot public-teleport-github-review-bot bot removed the request for review from codingllama April 30, 2024 19:54
@avatus avatus added this pull request to the merge queue Apr 30, 2024
@avatus avatus removed this pull request from the merge queue due to a manual request Apr 30, 2024
@avatus avatus force-pushed the avatus/device_badge branch from 5d9a30a to d162509 Compare April 30, 2024 20:31
@avatus avatus enabled auto-merge April 30, 2024 20:31
@avatus avatus added this pull request to the merge queue Apr 30, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Apr 30, 2024
@avatus avatus added this pull request to the merge queue Apr 30, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Apr 30, 2024
@avatus avatus added this pull request to the merge queue Apr 30, 2024
Merged via the queue into master with commit 15109b9 Apr 30, 2024
43 checks passed
@avatus avatus deleted the avatus/device_badge branch April 30, 2024 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Indicates that a PR does not require a changelog entry size/sm ui
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants