Why use a saved corporate login

The “Corporate login: username and password” method obtains a Cognos ticket with saved credentials. It is intended for background runs and shared flows that must operate with the defined TM1 permissions of one account. The password is stored encrypted.

Choose an account with access to the specific objects required. People running the flow may have different UBC Data Bridge permissions, but IBM sees this saved account.

Connection setup

  1. Select corporate login with username and password.
  2. Enter the username in the format required by the login form: a username or email address.
  3. Enter the Cognos namespace, password and gateway address.
  4. If the gateway redirects to another login host, add its exact hostname to “Login system hosts”. Do not enter a protocol, path or arbitrary wildcard.
  5. Click “Test”; after success, save the connection and check the flow in a test environment.

The connection's gateway_url field takes precedence over the installation gateway. The connection's allowed hosts supplement the hosts configured by the administrator through BRIDGE_CAM_LOGIN_HOSTS.

Supported login pages

Automatic login handles conventional HTML username and password forms, including suitable Cognos, Keycloak or AD FS configurations. Support depends on the actual form, not just the provider name.

This method cannot complete a second factor, mandatory password change, acceptance of terms or pages requiring browser execution. For interactive runs, use “From user session”. Automated runs require an organization-approved method that does not need interactive participation.

Ticket renewal and failures

The ticket is cached in encrypted form. The first request checks whether the cached ticket remains valid; UBC Data Bridge obtains a new one when necessary. A safe read request may be retried once after a 401 response. A request that changes data is not automatically retried.

After a login failure, further attempts are temporarily paused to avoid a series of failed logins. “Test” shows the cause: a blocked host, unsupported form, second factor, rejected credentials or network failure. Correcting saved credentials allows the new set to be tested.