Integrating Tivoli Access Manager (TAM) with WorkSite Web 8.2

Hi all,

We're looking at a project where we will need to have users log into our global web user list (which uses LDAP) via Tivoli Access Manager (TAM) and then have them access WorkSite Web 8.2 (WSW).

We want to avoid needing them to log in a second time to WSW, but can't see how to do it (short of having TAM authenticate them to Active Directory, which has several issues).

In WSW there is a Global Options area called Web Access Management that looks promising - it mentions a username header, which is an http header that contains the username. This sounds just how TAM works, and might allow us to have WSW trust TAM's authentication - provided there is an external user in WSW that matches that username.

Has anyone actually done this, or is a resident expert on these issues?

Thanks,
Angus

Find more posts tagged with

Comments

Falkayn

Hello? I was hoping to get more response on this question ...

bindingEx002.jpg

Migrateduser

WSW out of the supports reverse proxy solutions as long as reverse proxy puts HTTP Header variable for authenticated user. This means once you login via proxy server, WSW will recognize that and let you in without prompting WorkSite login dialog. This is all configured via "Web Access Management" Panel in Global Options. We have customers using this feature via "Site Minder" and Tivoli - For more information you can refer to WSW help file at
http://your server /WorkSite virtual directory /help/en/help/Web_Access_Management.htm

There was a known issue with Tivoli proxy in uploading a document from WSW. We have a hot fix available for that. You may want to contact interwoven technical support at worksite-support@interwoven.com

If you have any specific question, feel free to post it again

blob_clob.rptdesign

Falkayn

sheetaljain,

Thanks for the response. It sounds like we can rely on this, we're having our reseller contact check out whether the hotfix is already applied in WorkSite Web 8.2. I'm waiting for database access to setup the web server, but I will check that help file out as soon as I do.

Angus

Falkayn

Update: We have this working now, it is very cool. However there are two oustanding issues:

1. The WorkSite Link buttons in the Notes editor and Discussion Topic editor do not work. We have hacked around this for now, but it seems to not be encoding an "&" in the URL under TAM.

2. Import Document does not work with ActiveX control, however it does with the File Control. This suits us (it turns out), but I am wondering if the patch mentioned above is requried to 8.2.

Cheers,
Angus

Migrateduser

Falkayn

1) You mean Tivoli is not encoding it or WSW? If its WSW, you can submit a bug to our tech support

2) I think we have a patch lined up for 8.2 and 8.1. You can request it via techsupport

Also, I am intersted in what kind of solution you have built. Is it possible to demo me something?