Skip to Content.
Sympa Menu

cat-users - Re: [[cat-users]] Windows "Credential Installation Problem"

cat-users AT lists.geant.org

Subject: The mailing list for users of the eduroam Configuration Assistant Tool (CAT)

List archive

Re: [[cat-users]] Windows "Credential Installation Problem"


Chronological Thread 
  • From: Alberto Martínez Setién <alberto.martinez AT deusto.es>
  • To: Tomasz Wolniewicz <twoln AT umk.pl>
  • Cc: cat-users AT lists.geant.org
  • Subject: Re: [[cat-users]] Windows "Credential Installation Problem"
  • Date: Mon, 25 Mar 2019 18:20:24 +0100

 
I'm thinking of comparing both user_cred.xml files to see if there is any difference. Is there a parameter that prevents their removal?

If you run the installer with the -DEBUG-4 then the files will not be deleted.

Silly me... thanks.

$ sha1sum Downloads/user_cred.*.xml
4cd3bff63cbcf91b51fb28452dee0160cafe8c20  Downloads/user_cred.2018.xml
4cd3bff63cbcf91b51fb28452dee0160cafe8c20  Downloads/user_cred.2019.xml

Both XML files are identical. This means of course that the CAT tool works as intended.
My other suspect is the "WLANSetEAPUserDatax64.exe" program, which seems different from the previous "WLANSetEAPUserData64.exe", but I don't know how to debug that.

We are using https://github.com/rozmansi/WLANSetEAPUserData

As you can see the version has not changed for quite a while now.

At this point I'm pretty convinced that there is indeed some difference between the old WLANSetEAPUserData and the new.
I will do further testing calling the WLANSetEAPUserData program versions directly.

BTW, why the x in WLANSetEAPUserDatax64? And why that x doesn't appear at https://github.com/GEANT/CAT/tree/master/devices/ms/Files/WLANSetEAPUserData?

The current installer checks username for trailing spaces and removes them if found. I cannot imagine that a bug there could generate something but ...

No spaces or bogus characters here..

Can you confirm that the old version of the installer not only does not report any errors but actually stores the credentials correctly so that the user is able to connect?

That's correct. We didn't have any issue these last years.

Do you see the problem in more then one case? We did not get similar reports except for the one I mentioned and the case where the user had no permission to install a global user profile.

It seems to be more than one case, yes. Could that permission case explain why an old CAT version works but not a new one?




Archive powered by MHonArc 2.6.19.

Top of Page