Fixed a mistake in my prior documentation about oidc (happy to move that into...

Fixed a mistake in my prior documentation about oidc (happy to move that into a separate PR if you would like) (#263)

Added new table details page with badges

README.md

@@ -39,7 +39,7 @@ Please note that the mock images only served as demonstration purpose.
 
 - **Table Detail Page**: Visualization of a Hive / Redshift table
 
-    ![](docs/img/table_detail_page.png)
+    ![](docs/img/table_detail_page_with_badges.png)
 
 - **Column detail**: Visualization of columns of a Hive / Redshift table which includes an optional stats display
 

docs/authentication/oidc.md

@@ -110,9 +110,10 @@ Assumptions:
 2. You need to register amundsen in okta as an app. More info [here](https://developer.okta.com/blog/2018/07/12/flask-tutorial-simple-user-registration-and-login). 
 But here are specific instructions for amundsen:
     - At this time, I have only succesfully tested integration after ALL grants were checked.
-    - Set the Login redirect URIs to: http://amundsen-frontend/oidc_callback
+    - Set the Login redirect URIs to: `http://amundsen-frontend/oidc_callback`
     - No need to set a logout redirect URI
-    - Set the Initiate login URI to: http://amundsen-frontend/oidc_callback
+    - Set the Initiate login URI to: `http://amundsen-frontend/`
+        (This is where okta will take you if users click on amundsen via okta landing page)
     - Copy the Client ID and Client secret as you will need this later.
 3. At present, there is no oidc build of the frontend. So you will need to build an oidc build yourself and upload it to, for example ECR, for use by k8s.
    You can then specify which image you want to use as a property override for your helm install like so: