|
⇤ ← Revision 1 as of 2019-05-15 21:16:22
Size: 547
Comment:
|
← Revision 2 as of 2019-05-15 21:19:22 ⇥
Size: 1025
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
Repeat HW 11 but now hosting your website with Kestrel using ASP.NET core reverse proxied behind apache all running on your Google Compute instance. Show me: * Apache is running * Kestrel is running * That apache is accepting HTTPS connections and that you have a let's encrypt certificate working (note: apache should not accept HTTP connections) * That Kestrel is running HTTP * That your app authenticates southern.edu email addresses against google. |
HW12: Google Authentication on ASP.NET core and Google Compute Cloud
Repeat HW 11 but now hosting your website with Kestrel using ASP.NET core reverse proxied behind apache all running on your Google Compute instance.
Show me:
- Apache is running
- Kestrel is running
- That apache is accepting HTTPS connections and that you have a let's encrypt certificate working (note: apache should not accept HTTP connections)
- That Kestrel is running HTTP
- That your app authenticates southern.edu email addresses against google.
Hints:
- See HW11 Gotcha's and other information.
We were having problems determining how to get the system to use https for Google Redirect URIs instad of HTTP. We found a useful answer here.