Issue reported by @jarodreyes.
The user was not informed that `fleetctl login` was using the PASSWORD
environment variable:
`main`:
```sh
export PASSWORD=wrong
fleetctl login
Log in using the standard Fleet credentials.
Email: a@b.c
Error: Login failed: login received status 401 Authentication failed: Authentication failed
```
And with the changes on this PR:
```
export PASSWORD=wrong
fleetctl login
Log in using the standard Fleet credentials.
Email: a@b.c
Using value of environment variable $PASSWORD as password.
Error: Login failed: login received status 401 Authentication failed: Authentication failed
```
Closes: #12214
Changes:
- Upgraded the version of highlight.js we're using from `v9.10.0` to
`v10.7.3` to add support for YAML syntax highlighting.
- Updated highlight.js usage (`hljs.highlightBlock()`»
`hljs.highlightElement()`)
Created Rapid7 landing page in `/imagine`
From Mike T:
Sorry for the bombardment of commits. Here's a breakdown of those
commits and changes:
- I increased the max-width of the hero text area for M-size breakpoints
and above to suit the content better.
- During my review, I noticed that the local-preview-generated changes
to `.sailsrc` had been pushed, but in my attempt to fix I deleted the
file rather than the diff.
- Attempted to revert back to my previous commit, but this was my first
attempt at removing a commit, so I wasn’t sure if it was successful.
- In the end, I re-pushed `.sailsrc` from `main`. - Crisis averted in
a very roundabout way 🙏🏻
# Checklist for submitter
- [x] Manual QA by Mike T
---------
Co-authored-by: Mike Thomas <mthomas@fleetdm.com>
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Co-authored-by: Eric <eashaw@sailsjs.com>
Changes:
- Updated the bottom heading on pages generated by the landing page
generator to match our current landing page layout ("Think for yourself"
» "Lighter than air")
Closes: #12354
Changes:
- Added right margin to the first h1 in documentation pages to prevent
headings from overflowing onto the edit page button.
- Added a minimum height to the subtopics of documentation pages on
mobile screens to prevent the edit page button from being positioned
over the page's content.
Update verbiage.
---------
Co-authored-by: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com>
Co-authored-by: Andrew Baker <89049099+DrewBakerfdm@users.noreply.github.com>
This should allow us to pass in policies for kms and both s3 buckets.
This is needed in order to allow for the new sns alerting lambda to
query athena for 5xx errors.
Fixes a couple spots where "<organization>" wasn't displaying
because it was treated as a custom HTML element (and also fixes a
front-end error from Vue)
I got [nerd sniped](https://en.wikipedia.org/wiki/Nerd_sniping) while
adding the QA process for the website and did some long overdue
housekeeping of the brand section of the handbook. There's still more to
do, but this is a good start.
## Changes
- Updated the `maintainedby` meta tag on `commonly-used-terms.md`
- Added a line break that I spotted on `content-style-guide.md`
- Moved the docs handbook content to its own page and linked to it from
the marketing page of the handbook to reduce the excessive scroll.
- Consolidated the Markdown instructions from the docs handbook section
into `markdown-guide.md` and linked to it from the relevant section of
the docs handbook page.
- Moved the website handbook content to its own handbook page and linked
to it from the marketing page of the handbook to reduce the excessive
scroll.
- Added quality assurance process to the website handbook page.
- Re-ordered the brand section of the handbook to show brand resources
and content style guide first.
## QA
- [x] Manual QA for all new/changed functionality
Proposed changes:
- I spotted a typo
- I updated references to previous staff members while reading.
- I spelled out "Executive Assistant" in the first couple of instances
and included "(EA)." It may seem an obvious acronym, but I'm a dumbo,
and the first time I heard EA mentioned, I thought we were talking about
Electronic Arts, the software developer. That is not entirely true, but
you get my point 😉
There are also two more references to @mentioning Charlie in Slack on
lines 148 and 150 that I don't know who to update to, so I have left
them untouched for the time being.
Closes#11965
Changes:
- Updated the pricing table on the pricing page to be rendered by the
server.
- Updated the pricing page's view action to create another version of
the pricing table that does not have the "Device management" category
and that has security features sorted to the top of the table.
- Moved two features from the "Device management" category to "Security
and compliance" in `pricing-features-table.yml`.
Closes: https://github.com/fleetdm/confidential/issues/2964
Changes:
- Updated the `receive-from-customer-fleet-instance` webhook to send a
request to a Workspace One OAuth URL to get the authorization token used
to send requests to a Workspace one instance.
Before this is merged, we will need to:
- [ ] remove the `sails.custom.config.customerWorkspaceOneTenantId` and
`customerWorkspaceOneAuthorizationToken` config variables.
- [ ] Add two new config variables:
`sails.config.custom.customerWorkspaceOneOauthSecret` and
`sails.config.custom.customerWorkspaceOneOauthId`
.
