Question

Hello!

We are using TWiki in our company for some time now and want to allow some customers to contribute to our wiki. Is there a way to "reuse" their authentication from our website when entering the TWiki?

Since the look'and'feel of the TWiki is quite adjusted to the website it would be rather annoying to have to enter the username again.

I've been searching the docs for a while but still have no picture in mind: May I use a (session-) parameter in the URL; could the web-server set a cookie for the wiki; is apache of any help... ?

Thanks in advance

Mike [;-)

Environment

-- MikeHerzog - 24 Aug 2006

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

It depends what sort of authentication you are using, both for TWiki and for your customers. Template or Apache auth? Or are you using another auth contrib, such as LDAP? Why are your custoimers on a different auth system?

-- CrawfordCurrie - 28 Aug 2006

You can authenticate TWiki users with your existing AD or LDAP directory. You can use Apache authentication and delegate authentication to an Apache module such as Google:auth_ldap, or you can use a TWiki specific extension such as LdapContrib.

SSO (single sign-on, Google:WebSSO) goes one step further: Users are authenticated silently in the background, which is browser specific. See related topics TransparentAuthentication, NoIntranetUserLogon, TransparentAuthenticationRevisited.

-- PeterThoeny - 29 Aug 2006

Back again. Our customers reach the (internal) twiki via a public web site. These two are hosted on different http-servers (both apache). So the task is to (re-)use the authentication for the internal server. Currently there's a Java Servlet resposible for authetication on the public side, but this could changed as needed.

-- MikeHerzog - 08 Sep 2006

It's really difficult to give an authroatative answer with so little information, unfortunately. I'm not aware of any way to "pass on" authentication between servers, as the web browser caches authentication on the basis of the web site address. It all depends on how your customers get to your internal twiki. I think you need to talk to some apache experts, rather than the TWiki team.

-- CrawfordCurrie - 11 Oct 2006