From a3a53cf27993865590d57170fdc3ca7e5ee826a6 Mon Sep 17 00:00:00 2001 From: PrivateMeggido Date: Mon, 22 Dec 2014 09:53:55 -0800 Subject: [PATCH] Updated Sample Static Configuration for using Google Authentication (markdown) --- Sample-Static-Configuration-for-using-Google-Authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Sample-Static-Configuration-for-using-Google-Authentication.md b/Sample-Static-Configuration-for-using-Google-Authentication.md index 1acdf73..0c65a3f 100644 --- a/Sample-Static-Configuration-for-using-Google-Authentication.md +++ b/Sample-Static-Configuration-for-using-Google-Authentication.md @@ -22,7 +22,7 @@ The following example is based on making the sample simple-web-app to work with ``` -1. Configure the Google Server entry to use the OAuth2.0/OIDC endpoints Google uses. This is where the non-standard behaviors are addressed. The "issuer" is not prefixed with "https://" and thus a static configuration is needed, and Google processing does not ignore the "nonce" parameter, which required the audition of the "nonceEnabled" property. +1. Configure the Google Server entry to use the OAuth2.0/OIDC endpoints Google uses. This is where the non-standard behaviors are addressed. The "issuer" is not prefixed with "https://" and thus a static configuration is needed, and Google processing does not ignore the "nonce" parameter, which required the addition of the "nonceEnabled" property. ``` xml