Oracle^® Business Intelligence Enterprise Edition Deployment Guide > Implementing Single Sign-On Products With Oracle Business Intelligence > Sample Configuration Files >

Using an HTTP header with additional parameters

<?xml version="1.0"?>

<WebConfig>
   <ServerInstance>
   <!-- other settings ... -->
      <Listener>
         <Firewall>
            <Allow address="127.0.0.1"/>
            <Allow address="192.168.1.100/>
            <Allow address="192.168.1.101/>
         </Firewall>
   <!-- other settings ... -->
      </Listener>
   <!-- other settings ... -->
   <CredentialStore>
      <CredentialStorage type="file" path="<OracleBIData>/web/config/credentialstore.xml" passphrase="another_secret"/>
   <!-- other settings ... -->
   </CredentialStore>
   <!-- other settings ... -->
   <Auth>
      <SSO enabled="true">
         <ParamList>
            <!--IMPERSONATE param is used to get the authenticated user's username and is required -->
            <Param name="IMPERSONATE"
               source="httpHeader"
               nameInSource="x-Foo-SSO-GUID"/>
            <!--Optional, NQ_SESSION.LOCALE sets up the user's locale as determined by SSO system -->
            <Param name="NQ_SESSION.LOCALE"
source="cookie"
               nameInSource="FOO_SSO_LocaleID"/>
           <!--Optional, NQ_SESSION.P1 sets up some other parameter from SSO system -->
            <Param name="NQ_SESSION.P1"
               source="header"
               nameInSource="FOO_SSO_P1"/>
          </ParamList>
      </SSO>
   </Auth>
   <!-- other settings ... -->
   </ServerInstance>
</WebConfig>

This results in a connection string that takes on the following form:

UID=Impersonator;PWD=secret;IMPERSONATE=testuser;NQ_SESSION.LOCALE=en-GB;NQ_SESSION.P1=param1;