FMR Workbench - Revision history

Glenn: /* Disabling authentication */

2025-12-18T16:10:00Z

‎Disabling authentication

Glenn: /* Authentication */

2025-12-18T16:09:20Z

‎Authentication

Glenn: /* Authentication */

2025-12-18T16:08:03Z

‎Authentication

Glenn: /* Troubleshooting OIDC */

2025-12-18T16:05:17Z

‎Troubleshooting OIDC

Glenn: /* Authentication */

2025-12-18T16:03:10Z

‎Authentication

Glenn: /* Open ID Connect (OIDC) principles */

2025-12-18T16:03:01Z

‎Open ID Connect (OIDC) principles

Glenn: /* Basic Authentication */

2025-12-18T16:02:18Z

‎Basic Authentication

Glenn: /* OIDC Authorization Code Flow (standard) */

2025-12-18T16:00:48Z

‎OIDC Authorization Code Flow (standard)

Glenn: /* OIDC Authorization Code Flow with PKCE (Proof Key for Code Exchange) */

2025-12-18T16:00:36Z

‎OIDC Authorization Code Flow with PKCE (Proof Key for Code Exchange)

Glenn: Expand OIDC authentication configuration

2025-12-18T15:36:22Z

Expand OIDC authentication configuration

@@ Line 198: / Line 198: @@
 == Disabling authentication ==
-Authentication can be disabled for an environment by setting the authorisation method to <code>NONE</code>/
+Authentication can be disabled for an environment by setting the authorisation method to <code>NONE</code>.
 Workbench configuration example:

@@ Line 152: / Line 152: @@
 Clicking Login will take the user to the OpenID Connect login page (defined in the configuration file of the FMR-Workbench).  The user authenticates with the chosen OpenID Connect identity provider (IdP), on success the user is redirected back to the FMR-Workbench with a token.  The token is stored against the user's session, and used to authenticate with the target service.
-== OIDC Authorization Code Flow with PKCE (Proof Key for Code Exchange) ==
+=== OIDC Authorization Code Flow with PKCE (Proof Key for Code Exchange) ===
 If supported by your IdP, OIDC authorization code flow with PKCE provides additional security by eliminating the need for a static client secret and preventing authorization code interception.
@@ Line 163: / Line 163: @@
     },
-== OIDC Authorization Code Flow (standard) ==
+=== OIDC Authorization Code Flow (standard) ===
 Standard OIDC authorization code flow involves Workbench sending the client_id & client_secret to the IdP to get an auth_code, then using client_id & client_secret again to exchange the auth_code for access tokens.
@@ Line 175: / Line 175: @@
      },
-== Microsoft Entra ID ==
+=== Microsoft Entra ID ===
 Entra ID (previous Azure Active Directory or AAD) acts as an OIDC IdP.
@@ Line 189: / Line 189: @@
      },
-== Troubleshooting OIDC ==
+=== Troubleshooting OIDC ===
-=== 'invalid_client' Entra ID error AADSTS7000218 ===
+==== 'invalid_client' Entra ID error AADSTS7000218 ====
 Authentication fails reporting:
 * invalid_client
@@ Line 197: / Line 197: @@
 The IdP is not configured for PKCE. In these cases use the standard authorization code flow.
-== No authentication ==
+== Disabling authentication ==
 Authentication can be disabled for an environment by setting the authorisation method to <code>NONE</code>/

@@ Line 147: / Line 147: @@
 Workbench configuration example:
-  "auth":"BASIC"
+  "auth":"BASIC",
 == Open ID Connect (OIDC) ==
@@ Line 196: / Line 196: @@
 * The request body must contain the following parameter: 'client_assertion' or 'client_secret'
 The IdP is not configured for PKCE. In these cases use the standard authorization code flow.
 = Structure Navigation and Export =

@@ Line 190: / Line 190: @@
 == Troubleshooting OIDC ==
-=== PKCE not supported ===
+=== 'invalid_client' Entra ID error AADSTS7000218 ===
-Authentication failures reporting
+Authentication fails reporting:
 * invalid_client
 * Entra ID error <code>AADSTS7000218</code>
 * The request body must contain the following parameter: 'client_assertion' or 'client_secret'
-indicate the IdP is not configured for PKCE. In these cases use the standard authorization code flow.
+The IdP is not configured for PKCE. In these cases use the standard authorization code flow.
 = Structure Navigation and Export =

@@ Line 141: / Line 141: @@
 = Authentication =
-The FMR Workbench supports 2 forms of authentication with the connected service: Basic Authentication and OpenID Connect. The type of authentication is set up in the Config file of the FMR-Workbench.
+The FMR Workbench supports two forms of authentication with the connected service: Basic Authentication and OpenID Connect. The type of authentication is set up in the Config file of the FMR-Workbench.
 == Basic Authentication ==

@@ Line 145: / Line 145: @@
 == Basic Authentication ==
 Clicking Login will take the user to the FMR-Workbench login page where the user is invited to enter a username and password.  These details are stored in the FMR-Workbench against the user's session, and they are used whenever the user interacts with the target service.  An initial check is performed against the target server to ensure the credentials can be used to obtain some structures, if the check fails then the details are deemed to be invalid and will be discarded.
 == Open ID Connect (OIDC) principles ==