Trusted Authentication not working with USER_PRINCIPAL for 3rd Party application

Hi ,

We have configured Trusted Authentication on BI side and the 3rd party application ( portal ) is configured for SAML.

For SAML to work with BI ( integrate) we need Trusted Authentication working as well. Also, Tomcat has been made a SAML service provider

However, when the portal redirection occurs, its not allowing to SSO to BI once Trusted Auth is enabled.

Below are the settings in the web.xml of BOE that are made

<security-constraint>

    <web-resource-collection>

    <web-resource-name>OnJava Application</web-resource-name>

    <url-pattern>/BOE/BI</url-pattern>

    </web-resource-collection>

    <auth-constraint>

    <role-name>onjavauser</role-name>

    </auth-constraint>

</security-constraint>

<login-config>

    <auth-method>BASIC</auth-method>

    <realm-name>OnJava Application</realm-name>

</login-config>

As per the above setting, its trying to Authenticate the user from the tomcat-users.xml file, rather than SecureAuth.

Also, in the global.properties file, below entries have been made

sso.enabled=true

trusted.auth.user.retrieval=USER_PRINCIPAL

trusted.auth.user.namespace.enabled=     ( this is left blank as we have created an Enterprise account for the same user account in the same naming convention i.e firstname.lastname )

Are there any changes from the portal side that are needed to be added in the above code for Trusted Auth to work with SAML as the Admin guide does not provided the correct code for USER_PRINCIPAL

Individually SAML from SecureAuth and Trusted Auth from BI are working, but the handoff (response) is not happening from the Tomcat over to SecureAuth so as to authenticate the user

Also, is there any additional information that we need, so as to allow this to work.