Auth with CHECK_EMAIL or CHECK_KEY

Help
isomac
2007-10-15
2013-05-01
  • isomac

    isomac - 2007-10-15

    Hi,

    The Linux_Readme was really one of the most guiding ones I have ever found.
    I have made all the required IP and Port Settings and it is as well reachable via dyndns.org and NAPT.
    So quite clear what to do in:
    jlls1:/usr/local/dimdim # vi dimdim.properties

    But one i tried to change
    ##      Authentication policy, valid values are: CHECK_EMAIL, CHECK_KEY, NO_CHECK
    dimdim.authenticationPolicy=CHECK_EMAIL
    or
    dimdim.authenticationPolicy=CHECK_KEY

    I get no presenter authorised.

    I tried:

    jlls1:/usr/local/dimdim/ConferenceServer/apache-tomcat-5.5.17/webapps/dimdim/WEB-INF # vi dimdimPresenters.txt
    #admin@dimdim.com,bugsbunnyshow
    user@domain.eu,presenter_name
    user@domain.eu,meeting_key
    user@domain.eu

    and nothing worked.

    Or in addintion:
    jlls1:/usr/local/dimdim/ConferenceServer/apache-tomcat-5.5.17/webapps/dimdim/WEB-INF # vi dimdimKey.txt
    checkkey
    user@domain.eu,presenter_name
    user@domain.eu,meeting_key
    user@domain.eu

    What for is
    jlls1:/usr/local/dimdim/ConferenceServer/apache-tomcat-5.5.17/webapps/dimdim/WEB-INF # vi dimdimAdmins.txt
    #admin,bugsbunnyshow
    if i do the customisation of the screen anyhow as root??? And there is no link in dimdim.properties toward that. So, what is this good for?

    Googl was not of big helped and I am elaborating for days, now.
    Help is really appreciated.
    I like the tool very much but Authrisation would be a must.

    Many many thanks,

    Juergen

    BTW: Is there some forced https for the presenter and clients available, which I have overlooked?

     
    • isomac

      isomac - 2007-10-15

      Hi,

      Me again with some more comments...

      I have read before
      Help with authentication check_key      jbedgood      3      2007-10-03 13:17
      but it had not really enlighted me.
      Sorry.

      jlls1:/usr/local/dimdim # vi dimdim.properties
      ##      File cotainning the list of emails authorized to present conferences.
      dimdim.presenterEmailsFile=dimdimPresenters.txt
      ##      File cotainning the list of emails authorized to present conferences.
      dimdim.dimdimAdminsFile=dimdimAdmins.txt
      ##      File cotainning the scheduled conferences.
      dimdim.conferenceSpecsFile=dimdimConferenceSpecs.dmc
      ##      Key file for the check key authentication policy.
      dimdim.keyFile=dimdimKey.txt

      Trying to find:
      jlls1:/usr/local/dimdim # find ./ -name dimdimConferenceSpecs.dmc
      has delivered no results
      ????

      And with
      dimdimPresenters.txt
      dimdimKey.txt
      I have the already described problems to properly use them for Authorisation.

      Hope that is giving well enough input to give me some guidance.

      Thanks and cheers,

      Juergen

       
    • isomac

      isomac - 2007-10-22

      Hi,

      Found out now and want to share.

      jlls1:/usr/local/dimdim # vi dimdim.properties
      dimdim.authenticationPolicy=CHECK_EMAIL

      The template file of:
      jlls1:/usr/local/dimdim/ConferenceServer/apache-tomcat-5.5.17/webapps/dimdim/WEB-INF # vi dimdimPresenters.txt
      is a bit misleading with:
      #admin@dimdim.com,bugsbunnyshow
      because it suggests that access control validates combination of email AND meetingname/topic (=bugsbunnyshow)

      Using email only will do the trick.

      jlls1:/usr/local/dimdim/ConferenceServer/apache-tomcat-5.5.17/webapps/dimdim/WEB-INF # vi dimdimPresenters.txt
      user@domain.eu

      This is quite a minimal security level and allow presenter access by some good guessing of participants.

      Sure, the dimdim team seems working hard on a lot of fronts and doing an outstanding job. Probably this will show up again on the priority list at the right time.

      Cheers,

      Jürgen

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks