Hi there,

Looking for some assistance on Trac Integration.

We use the Community version of Klaros Test Management.

With TRAC we use windows autentication to connect to it rather than having to enter our login credentials over and over again. However, the initial train of thought is to use Community version of Klaros for our test case management until such times we feel necessary to expand it further.

We have encountered a problem with intrgration with TRAC where KLAROS is trying to use NTLM instead of acceptin guser login credentials.

I was wonering if anyone could help us out with a way we can get round this problem?

I suppose what we really want to do is have the user enter username and password to access TRAC when logging a defect rather than use the LDAP in this case without getting messages that they cant be authenticated.

Thanks for your input

We haven't as of yet but I can suggest it to the man incharge of the installation.

Besides this option, are there other ways around it? Just thinking that if I supply a couple of options, they can choose the best one they feel works in our environment

Morning Torsten.

Sorry for not coming back sooner and forgive me if I have not explained things right. below is how we log into our network and TRAC normally follwoed by the problems we have for KLAROS login.

1. Network loging is usually <DOMAIN>\<Username> and then a password..
2. Once I have authenticated to the network. and Access TRAC my credentials are passed on to TRAC so that I do not need to log in twice.


KLAROS

1. We are using community so we do not have the LDAP functionality.
2. Login into KLAROS ( I set up a username and password same as my network password.
3. I ran a test and clicked to log a defect. I got asked for username and password.
4. I entered <DOMAIN>\<Username> as username then my network password. no connection made
5. Tried with just my username without domain. no connection made.

We have managed to get Klaros to recognise our instance of TRAC and tested the connection it works. But when we checked at a command prompt on the server, we could see that on login to TRAC for defect logging. nothing was happening. It seems to be trying an NTLM connection first and if it cant connect that way it does nothing more.

Hope that explains it better for you. If not I will have the guy installing Klaros for me, drop you a message explaining what he gets

Regards

Jamie

Hi Torsten,

We definitely have the plugin in place and working as we use it for another tool also.

I just emailed some screen shots to the support email address as I thought they might come in handy

We seem to be on TRAC 0.12

Hi Jamie,

I think I pinned down the source of your problems. The problem is rooted in the fact that we require non-authenticated access to the XML RPC plugin on the trac server side during authentication.

If you have raised the debug level in your trac installation you probably find lines like the following:



To circumvent this you must give the access rights to the XML-RPC plugin to non authenticated users as well as authenticated ones as shown below:



And yes this should have been part of the documentation ... so sorry for the hassle. If possible we will try to avoid requiring unauthenticated access (I don't like this) - I will keep you updated on further progress.

HTH - thanks for your support,

Regards, Torsten

P.S.: The Mylyn access was just to crosscheck the availability of the service.

Hi Torsten and Happy New year to you and your team.

I can now confirm that if I use the create Issue option. I can now log TRAC tickets. However, if I am executing a test and choose to log an issue at that stage. it will ask me for a username and password. No matter what username and password I supply at that stage, it will say it is incorrect.

Hi Torsten. Looks like it's righted itself.

I performed a Cache clear out of my browser and then restarted the browser. It now seems to work.

The initial attempt to login will ask me for my username and password because my KLAROS login is different to my TRAC login. As soon as I enter details (In my circumstances <Server>\<username> followeed by password) then it logs in successfully. I raised a couple of dummy tickets. All working well by the looks of it.

Thanks to you and your team for your efforts on this one.

Unfortunately Unable to test that for you. I only have community version.

What I can do as a form of test would be to set a user up in community that is an exact match to my TRAC NTLM user account.

Otehr than that, I am afraid I cannot do. Will come back to you shortly

Ok tested by creating a user to be the exact same as my NTLM user.

Authentication with TRAC worked without asking for username and password again.

Not a clean test of the NTLM feature available in Enterprise though. Any plans to have such a facility available in Community version?