Fix the description of login-service post-deploy fix for UMA lifetime

docs/eoepca/login-service.md

@@ -89,15 +89,17 @@ The deployment of the Login Service has been designed, as far as possible, to au
 
 ### UMA Resource Lifetime
 
-The Login Service maintains a background service that 'cleans' UMA resources that are older than aa certain age - by default 30 days. This lifetime does not fit the approach we are adopting, and so we must update this lifetime value to avoid the unexpected removal of UMA resources that would cause unexpected failures in policy enforcement.
-
-The client that is created by the script `./deploy/bin/register-client` (as per above) needs to be manually adjusted using the Web UI of the Login Service...
+The Login Service maintains a background service that 'cleans' UMA resources that are older than aa certain age - by default 30 days (`2592000` secs). This lifetime does not fit the approach we are adopting, and so we must update this lifetime value to avoid the unexpected removal of UMA resources that would cause unexpected failures in policy enforcement.
 
 * In a browser, navigate to the Login Service (Gluu) - https://auth.192-168-49-2.nip.io/ - and login as the `admin` user
-* Open `OpenID Connection -> Clients` and search for the client created earlier - `Application Hub`
-* Fix the setting `Authentication method for the Token Endpoint`  for the `ApplicationHub` - `client_secret_post` -> `client_secret_basic`
-* Save the update
-
+* Open `Configuration -> JSON Configuration -> OxAuth Configuration`
+* Search for the setting `umaResourceLifetime`
+* Update the values of `umaResourceLifetime` to `2147483647`
+* Select to `Save Configuration`
+* Restart the `oxauth` deployment...<br>
+  ```
+  kubectl -n um rollout restart deploy/login-service-oxauth
+  ```
 
 ## Login Service Usage