Although Smart View is a thick client and not a browser, it connects to server components using HTTP and behaves much like a browser from a system perspective. Smart View supports all standard web-based integration methods that browser interfaces support. However, there are some limitations:
Smart View is not supported in Kerberos-enabled environments.
SSO mechanisms are supported for shared connections only. SSO mechanisms are not supported with private connections, which are used primarily for backward compatibility.
If Smart View is launched from an existing browser session that is connected to an EPM System component, users must sign into Smart View again because it does not share the cookie from the existing session.