Help IndexTable of Contents

Networking

Proxy Settings

The BI Office Geo-Spatial solution uses Internet access on the client browser and on the application server. In case a proxy server is set on the LAN as a gateway for an Internet connection, it should be configured by providing the address and related settings for the proxy server.

IP Resolution

The IP Resolution switch should be used when different addresses for machines have been used, and you would like the application to attempt to resolve them to the same address when launching queries. Often this can produce erroneous results, especially in load balanced environments or with clustered data sources.

Multi Tenancy

Multi-Tenancy disables the functionality for users to create folders under the root folder of Public or Groups. However, an admin user can create folders in the root folder of Public and Groups.

NOTE: Only users with an Enterprise license will see the Multi-Tenancy option.

Token Authentication for NTLM Fallback

In cases when MS Kerberos fails or is not used, BI Office includes an option for “NTLM fallback” which allows authentication to BI Office and SSAS cubes for specific users using NTLM credentials. Use of the NTLM fallback option does not imply that the application is running in a less secure mode, but it does allow for the application to operate in environments where:

  • Kerberos tokens fail.
  • Kerberos tokens are intermittently available.
  • There exist complex domain models (where Kerberos is not possible).

For the NTLM feature to operate, the following prerequisites are required:

  1. The installation must use an Active Directory.
  2. The user account set in the “data source user” setting must have administrative rights on the target Analysis Services.
  3. SSAS services must be running under a network user or domain user (local services/users will not work).

If your implementation does not meet either of these standards, do not enable this the NTLM feature or your installation may not connect to Analysis Services successfully.

The two following Authentication parameters are related to the NTML fallback.

  • Support Effective Tokens - This parameter must be turned ON in order for NTML to function.
  • Inject user name into custom data field - This is an optional parameter for NTML processing.
User Group Lookup for Authentication

These three parameters affect the efficiency of user group lookup by BI Office during the authentication process. If authentication time is lagging, you can use these parameters to tweak response time.

  • Lazy Groups Lookup - When enabled, user authentication employs existing group information (based on parameters gathered from first-time authentication).
  • Support Nested Groups - When enabled, user authentication supports nested user groups. If your company does not use nested groups, you may turn this option OFF to save processing time.
  • Use Directory Cache - When enabled, user authentication supports active directory caching.

 

Home | Table of Contents | Index | User Community
Pyramid Analytics © 2011-2018