fix(docs): remove oxtrust references (#7390)

* fix(docs): remove oxtrust reference

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

* fix(docs): remove oxtrust reference

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

* fix(docs): remove oxtrust reference

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

* fix(docs): remove oxtrust reference

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>

---------

Signed-off-by: ossdhaval <343411+ossdhaval@users.noreply.github.com>
Co-authored-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>

docs/admin/config-guide/openid-connect-client-configuration.md

@@ -204,7 +204,7 @@ Getting access token for scope https://jans.io/oauth/config/openid/clients.reado
     ],
     "applicationType": "web",
     "contacts": null,
-    "clientName": "oxTrust Admin GUI",
+    "clientName": "Admin GUI",
     "idTokenTokenBindingCnf": null,
     "logoUri": null,
     "clientUri": null,
@@ -631,7 +631,7 @@ Calling with params limit=2
     ],
     "applicationType": "web",
     "contacts": null,
-    "clientName": "oxTrust Admin GUI",
+    "clientName": "Admin GUI",
     "idTokenTokenBindingCnf": null,
     "logoUri": null,
     "clientUri": null,

docs/admin/install/setup.md

@@ -94,7 +94,7 @@ To check usage of this script run help command
                      [-test-client-redirect-uri TEST_CLIENT_REDIRECT_URI] [--test-client-trusted]
 ```
 
-Use this script to configure your Jans Server and to add initial data required for oxAuth and oxTrust to start. If setup.properties is found in this folder, these properties will automatically be used instead of the interactive setup.
+Use this script to configure your Jans Server and to add initial data. If setup.properties is found in this folder, these properties will automatically be used instead of the interactive setup.
 
 Below are the optional arguments:
 

docs/casa/administration/2fa-basics.md

@@ -65,8 +65,12 @@ they normally don't demand special conditions from the device used to access, li
 
 To do so, just add a new configuration property named `2fa_requisite` to the custom interception script corresponding 
 to the authentication method, and assign `true` as its value. It may take more than one minute for Casa to pick up the 
-changes. To add the property, open oxTrust web console and navigate to `Configuration` > `Manage custom scripts`, 
-collapse the method you want to set as requisite for 2FA, and click on `Add new property`.
+changes. To add the property to a custom interception script, open 
+[the text-based UI (TUI)](../../admin/config-guide/config-tools/jans-tui/README.md) 
+and 
+navigate to 
+`Scripts`. Select and open the script. Use `Config properties` section to 
+add the new property.
 
 You can flag more than one method as requisite. In this case users will be encouraged to enroll one credential 
 associated to any of the flagged methods.

docs/casa/administration/faq.md

@@ -76,7 +76,7 @@ For Time-based OTP, ensure the time of your server is correctly synchronized (us
 
 Big time differences can cause unsuccessful attempts to enroll TOTP credentials in Casa.
 
-For Event-based OTP (HOTP), ensure you are using a suitable value for `look ahead window` (we suggest at least 10). Check contents of file `/etc/certs/otp_configuration.json`. If you apply editions, it is recommended to press the "Update" button of the "Manage Custom Scripts" form in oxTrust and wait a couple of minutes before retrying..
+For Event-based OTP (HOTP), ensure you are using a suitable value for `look ahead window` (we suggest at least 10). Check contents of file `/etc/certs/otp_configuration.json`. If you apply editions, it is recommended to wait a couple of minutes before retrying..
 
 ### The user interface is not showing any means to enroll credentials