Skip to main content

Connector Specific Authentication

  • Updated

The force connector in BOC products is used to explicitly enforce a specific authentication mechanism (connector) for user login, regardless of the system's default authentication settings. This is achieved by adding a corresponding URL parameter.

Common use cases include

  • When using a BOC product that is hosted in the BOC cloud (SaaS). The admin user (e.g., pp123456_admin) provided by BOC is only able to log in via a standard login.
  • Testing different authentication mechanisms in multi-system environments (e.g., SSO, Standard login, IDM login).
  • Supporting troubleshooting or user assistance (e.g., switching between login methods without altering the system configuration).
  • Providing situational access for specific user groups with special authentication requirements.
     

Referenced name and type parameters in force connector


Force Specific Connector


In order to force a specific connector, you need to adapt the URL as follows:

On premise - BOC product in your own Infrastructure

  •  <ENVIRONMENT-URL>/auth.view?forceConnector=<CONNECTOR_NAME>

Cloud (SaaS) - BOC product hosted by us

  •  https://example-pp123456.boc-cloud.com/auth.view?forceConnector=<CONNECTOR_NAME>

Example

You have multiple SAML connectors present in your configuration, and you want to create and distribute a URL which forces the SAML 2 connector (connector id="SAML 2"). 

In this example, you are operating ADONIS version 16.4, and the IP address of the Tomcat server is 10.2.100.68. Therefore, the URL should be formatted as follows:

Please note

With some Browsers, URLs cannot contain spaces, therefore the space character is replaced with "%20" in the example below (URL Encoding).

http://10.2.100.68:8000/ADONIS16_4/auth.view?forceConnector=SAML%202

 

Force Specific ConnectorType
 

In order to force a specific ConnectorType:

  • Navigate to <ENVIRONMENT-URL>/auth.view?forceConnectorType=<CONNECTOR_TYPE>

The first configured and applicable (not ruled out via constraints) connector of the specified type will be used for authentication.

Example

You intend to create and distribute a URL that enforces a connector of the type "IDM." You are operating ADONIS version 16.4. The IP address of your Tomcat server is 10.2.100.68. The URL should be formatted as follows:

http://10.2.100.68:8000/ADONIS16_4/auth.view?forceConnectorType=IDM

 

Force ConnectorName/ConnectorType for Administration

You can also force the use of a specific connector or connector type to log on to the administration of your BOC Product.

In order to force a specific connector, based on his name:

  • Navigate to <ENVIRONMENT-URL>/admin.view?forceConnector=<CONNECTOR_NAME>

In order to force a specific connector type:

  • Navigate to <ENVIRONMENT-URL>/admin.view?forceConnectorType=<CONNECTOR_TYPE>

The first configured and applicable (not ruled out via constraints) connector of the specified type will be used for authentication.

 

Force Refresh of Connector Data

When the parameters above are used, information about the selected connector is stored in your browser cache. This cached data will be reused for all subsequent sessions, unless all browser windows are closed.

Please note

If you access the force connector using an incognito browser, the connector will not be stored in the browser cache, and the steps below are not necessary.

To log into the environment using a different connector than the one stored in the cache, you may do one of the following:

  • Modify the URL to specify the desired connector or connector type
  • Close all open browser windows
  • Clear the browser cache to restore the default connector settings

 

Related articles