Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

Help with authentication check_key

Help
2007-09-20
2013-05-01
  • Joshua Bedgood
    Joshua Bedgood
    2007-09-20

    I am trying to understand the setting for check_key in the dimdim.properties file but I can not find any documentation about it.  Can someone please explain how to use this setting?

    Thanks,
    Josh

     
    • There is a basic authentication check in the product which allows you to specify restricted presenter email-ids or conference key who have the privilege of starting conferences.

      To use this feature, you need to do the following:-

      1) Edit the dimdim.properties file to change the following:-
      dimdim.authenticationPolicy=NO_CHECK
      to 
      dimdim.authenticationPolicy=CHECK_EMAIL
      or
      dimdim.authenticationPolicy=CHECK_KEY
      (default location - C:\Program Files\Dimdim\Conference Server\Tomcat 5.5\webapps\dimdim\WEB-INF\classes\resources) 

      2) The file containing authorized email ids / Conferencekeys is specified in the dimdim.properties file as:-

      ## File cotainning the list of emails / conf keys authorized to present conferences.
      ##
      dimdim.presenterEmailsFile=dimdimPresenters.txt
      You can leave this as default. 

      3) Save the dimdim.properties file. Open the dimdimPresenters.txt file
      The default location of this file is C:\Program Files\Dimdim\Conference Server\Tomcat 5.5\webapps\dimdim
      Add the email-ids or conf-keys of the presenters in the file - one on each line.

      4) Save the file and restart the conference server. Only authorized email ids / conference keys can start meetings now.

      Please let me know if this helps.

      Regards,
      -Rajesh

       
      • thorsten
        thorsten
        2008-02-29

        No it does not help. It`s the same message, "User not authorized"

        Could you please test it?

        Regards Thorsten

         
    • Hello,

      if you are using check_key, you need to modify

      ##
      ##    Key file for the check key authentication policy.
      ##
      dimdim.keyFile=dimdimKey.txt

      instead of step 2 as mentioned above.

      Regards,
      -Rajesh

       
    • romgo
      romgo
      2007-10-03

      Hi,

      I've got the same problem :

      in the wrapper.log i've got :

      INFO   | jvm 1    | 2007/10/03 17:06:36 | Action redirect data:null-null-null-null-null-null-null
      INFO   | jvm 1    | 2007/10/03 17:06:37 | Security key must be: -checkkey-
      INFO   | jvm 1    | 2007/10/03 17:06:37 | StartNewConferenceCheck returning:error, result code:USER_NOT_AUTHORIZED, message:User not authorized

      I put the good meeting key (the as the file dimdimKey.txt. I've restarted the server.

      my dimdim.propeties like :

      dimdim.keyFile=dimdimKey.txt => located in /usr/local/dimdim/ConferenceServer/apache-tomcat-5.5.17/webapps/dimdim/
      dimdim.authenticationPolicy=CHECK_KEY

      I'm running dimdim under Debian 4.0

      Any idea ?

      Thank's

       
    • isomac
      isomac
      2008-03-18

      Hi,
      I had similar problems with the 1.6 Alpha.
      Check under my nick in october last year or so.
      I made some comments on how i made it work.

      Cheers

      Jürgen