nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Teamsite Authentication

System

Hi Guys,

We have a scenario where we are integrating Teamsite with an internal web application. The way we planned to do is User logs in with his/her credentials using Teamsite login screen, after the authentication user will be taken to either std/pro interface where we show custom links to the internal web application. User clicks on the links and it launches a new window with the internal application.

The problem that we are facing is : In TS screen we have a logout button, if user clicks on logout it logs out of Teamsite but he/she is still able to continue with the new window which has the internal application. Its applicable in the reverse case also where user logs out from internal application but still able to continue working with Teamsite. Our requirement is when user clicks on logout from either TS or the internal application, he/she should be logged out of both the applications. Has anybody handled this scenario before.

Any pointers?

TS version: 6.7.2
OS : Windows 2003
LDAP authentication.
Internal application runs on Tomcat on a different JVM.

Thanks,
Arun.

Find more posts tagged with

Comments

Samir_Friend

You might have to introduce a middle tier[a common API or library] in between Teamsite and your external application to do the session-management for you if both are independently authenticating the users using the LDAP.

I think in the VFE, there is an option to authenticate user for its use(not sure though) and VFE is an external application embedded into Teamsite. You might get a hint from the VFE guides on how it is managing the session across Teamsite.

Your other option however could be to use Teamsite authentication for the external app instead of doing independent authentication using your LDAP. In case it is implemented, another view of looking at this problem would be how your SSO is implemented in this scenario(I am assuming it is implemented since user is able to log on to your external app after login onto Teamsite) - whether it enterprise or federation SSO, you might have to check if it is implemented correctly.