chore: add HTTPS req for PWA & update OIDC claims

ericpaulsen · ericpaulsen · commit ae74250bbed0 · 2022-03-30T13:58:39.000-05:00
diff --git a/admin/access-control/manage.md b/admin/access-control/manage.md
@@ -14,19 +14,20 @@ If you opt for **OpenID Connect**, you'll need to provide additional
 configuration steps, which are detailed in the subsequent sections of this
 article.
 
-## Requirements
+## Coder's OIDC claims
 
 Coder expects the following [OIDC claims](https://developer.okta.com/blog/2017/07/25/oidc-primer-part-1#whats-a-claim)
 from your OIDC provider:
 
-- `email`
+- `email` (required)
 
 - `name` (full name/display name)
 
 - `preferred_username` (username for dev URLs)
 
 You may need to map these to your existing claims within your OIDC provider's
-admin console.
+admin console. If `name` and `preferred_username` are not provided, Coder will
+derive both claims from the email address.
 
 ## Set up OIDC authentication
 
diff --git a/workspaces/pwa.md b/workspaces/pwa.md
@@ -9,7 +9,8 @@ experience akin to a native application and improved performance.
 
 ## Requirements
 
-To use Coder as a PWA, you must be using Google Chrome or Microsoft Edge.
+To use Coder as a PWA, you must connect to Coder over HTTPS and use either
+Google Chrome or Microsoft Edge.
 
 ## Installing the PWA
 
