Its couple of months now since my last post part(i) and that project went nowhere.
Now suddenly one more requirement came and re-org happened so suddenly integrating TAMe became necessity.
Its was decided by security team to stick with Junction approach.
1) Create a NT auth based Sharepoint site, at default zone.
2) Create Forms based extension in any other zone.
3) Junction this Forms based extension with TAMe.
4) PDF were show properly but none of the word or excel documents. The trick was to disable client integration for the document library.
5) Today Nov 15 2010 the search is not working when accessed through TAMe
This issue has been fixed. Our IIS admin had added an entry for host header - sw999
Once we removed this explicitly added host header entry
and added sw999.xxx.domaijavascript:void(0)n.ext entry in AAM (Alternate Access Mapping),
Search started working.
Search was sending requests for sw999.xxx.domain.ext which we had to enter in AAMs
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment