update doc for google id

README.md

@@ -92,7 +92,7 @@ The filter relies on the spark [spark.ui.filters](https://spark.apache.org/docs/
 | `cookie-max-age-minutes`   | `AUTH_COOKE_MAX_AGE_MINUTES`  | 12 * 60 | The maximum spark-cookie cookie duration in minutes                                                                                                                                                                                                            |
 | `cookie-cipher-secret-key` | `AUTH_COOKIE_ENCRYPTION_KEY`  |    -    | Cookie encryption key</br> Can be generated using: `openssl enc -aes-128-cbc -k <PASS PHRASE> -P -md sha1 -pbkdf2`                                                                                                                                             |
 | `cookie-is-secure`         | `AUTH_COOKE_IS_SECURE`        |  true   | When enabled, the cookie is transmitted over a secure connection only (HTTPS).</br> Disable the option if your run with a non secure connection (HTTP)                                                                                                         |
-| `user-id`         | `AUTH_USER_ID`        |  email   | * `email`: set the id seen by spark acls as the email filled in the access token. </br> * `sub`: set the id seen by spark acls as the sub filled in the access token.                                                                                                          |
+| `user-id`         | `AUTH_USER_ID`        |  email   | * `email`: set the id seen by spark acls as the email filled in the access token. </br> * `sub`: set the id seen by spark acls as the sub filled in the access. </br> * `google`: set the id to the sub sent by google but remove the prefix 'account.google.com:'.                                                                                                          |
 | `jwt-header`         | `JWT_HEADER`        |  jwt_token   | Header that may contain the JWT Token that will be used for authentication. If not present, it will fall back with the default autentication workflow with a redirection on the login page.                                                                                                          |
 | `jwt-header-signing-alg`         | `JWT_HEADER_SIGNING_ALG`        |  RS256, ES256   | Signature algorithm used to verify the JWT Token provided.                                                                                                         |
 | `jwt-header-issuer`         | `JWT_HEADER_ISSUER`        |  issuer-uri from well known configuration | Issuer if different from the default issuer uri retrieved from the well known configuration fetched with 'issuer-uri' parameter.                                                                                                        |