4 files changed, 46 insertions, 2 deletions

diff --git a/issues/gn-auth/email_verification.gmi b/issues/gn-auth/email_verification.gmi
index fff3d54..07e2b04 100644
--- a/issues/gn-auth/email_verification.gmi
+++ b/issues/gn-auth/email_verification.gmi
@@ -12,7 +12,7 @@
 
 When setting up e-mail verification, the following configurations should be set for gn-auth:
 
-SMTP_HOST = "smtp.uthsc.edu"
+SMTP_HOST = "smtp.uthsc"
 SMTP_PORT = 25 (not 587, which is what we first tried)
 SMTP_TIMEOUT = 200 # seconds
 
diff --git a/issues/gn-auth/fix-refresh-token.gmi b/issues/gn-auth/fix-refresh-token.gmi
index 1a6a825..222b731 100644
--- a/issues/gn-auth/fix-refresh-token.gmi
+++ b/issues/gn-auth/fix-refresh-token.gmi
@@ -2,7 +2,7 @@
 
 ## Tags
 
-* status: open
+* status: closed, obsolete
 * priority: high
 * assigned: fredm
 * type: feature-request, bug
@@ -51,3 +51,8 @@ This actually kills 2 birds with the one stone:
 
 * Get the refresh token from the cookies rather than from the body
 * Maybe: make refreshing the access token unaware of threads/workers
+
+
+## Close as Obsolete
+
+We no longer do refresh tokens at all, they were a pain to look into, so I simply removed them from the system.
diff --git a/issues/gn-auth/pass-on-unknown-get-parameters.gmi b/issues/gn-auth/pass-on-unknown-get-parameters.gmi
new file mode 100644
index 0000000..a349800
--- /dev/null
+++ b/issues/gn-auth/pass-on-unknown-get-parameters.gmi
@@ -0,0 +1,17 @@
+# Pass on Unknown GET Parameters
+
+## Tags
+
+* status: open
+* priority: medium
+* type: feature-request, enhancement
+* assigned: fredm, zsloan
+* keywords: gn-auth, authorisation
+
+## Description
+
+A developer or user could be needing to access some feature hidden behind some flag (so called, "feature flags"). Some of these flags are set using known (to the application and developer/user) GET parameters.
+
+If the user provides these get parameters before login, then go through the login process, the unknown GET parameters are dropped silently, and the user has to them manually set them up again. This, while not a big deal, is annoying and wastes a few seconds each time.
+
+This feature request proposes to pass any unknown GET parameters untouched through the authentication/authorisation server and back to the authenticating client during the login process, to mitigate this small annoyance.
diff --git a/issues/gn-auth/rework-view-resource-page.gmi b/issues/gn-auth/rework-view-resource-page.gmi
new file mode 100644
index 0000000..2d6e145
--- /dev/null
+++ b/issues/gn-auth/rework-view-resource-page.gmi
@@ -0,0 +1,22 @@
+# Rework "View-Resource" Page
+
+## Tags
+
+* status: closed, completed
+* priority: medium
+* type: enhancement
+* assigned: fredm, zsloan
+* keywords: gn-auth, resource, resources, view resource
+
+## Description
+
+The view resource page ('/oauth2/resource/<uuid>/view') was built with only Genotype, Phenotype, and mRNA resources in mind.
+
+We have since moved on, and added more types of resources (group, system, inbredset-group, etc). This leads to the page breaking for these other types of resources.
+
+We need to update the UI and route to ensure the page renders correctly for each type, or at the very least, redirects to the correct page (e.g. in the case of groups, which have a separate "view group" page).
+
+
+## Close as complete
+
+This is fixed now.