Alan Parra 626ec2a484 Update U2F App ID guidance in documentation (#8434) ...

Update U2F documentation to not include port 443 in the U2F App ID.

This is recommended by the standard, plus including port 443 in the App ID
causes issues with Chrome, as explained at #8017[1]. Non-standard ports are fair
game and should be included.

References:
* https://fidoalliance.org/specs/fido-u2f-v1.0-ps-20141009/fido-appid-and-facets-ps-20141009.html#determining-the-facetid-of-a-calling-application
* https://developers.yubico.com/U2F/App_ID.html
* https://www.npmjs.com/package/u2f-api#user-content-common-problems

[1] https://github.com/gravitational/teleport/issues/8017#issuecomment-931594038

* Update U2F App ID guidance in documentation
* Fix u2f.device_attestation_cas in Terraform docs

2021-09-30 13:47:25 -07:00

..

guides

Update U2F App ID guidance in documentation (#8434)

2021-09-30 13:47:25 -07:00

architecture.mdx

Try mini-diagrams and update launchpad titles (#7684)

2021-07-26 09:14:26 -07:00

faq.mdx

moves sso, labels and nodes to setup (#8216)

2021-09-13 11:49:17 -07:00

getting-started.mdx

Switch bash to code component (#8019) (#8029)

2021-08-23 11:30:02 -07:00

guides.mdx

Update cloud and add U2f guide (#7585)

2021-07-16 18:39:03 -07:00

introduction.mdx

Sasha/fwd fixes (#7881)

2021-08-11 16:05:41 -07:00