Forum LAMS for Tech-Heads - General Forum: Re: Re: permissions issues in LAMS 2.02

By: Fiona Malikoff

[ Reply | Forward ]

2.0 had the same bug in it, so rolling back would be a BAD idea.

I'm not sure why it worked last year. The problem only occurs if the user is a Learner in ALL courses - if they are an Author or some other privilege in another course then you won't see the problem.

It will be fixed in 2.0.3 (I've already checked in the change) but I can't promise 2.0.3 in the next week, so you need a work around.

Option (1) Create a new course and put all of your learners in that course and give them authoring or monitoring rights. Now they'll work. As they have the more powerful rights in a different course, they can't do any "damage" to the proper course. Mind you, they will wonder about the new buttons on the screen. Then your sequence should work.

Option (2) Fix the actual bug! You can do this if you are comfortable unzipping and rezipping .war files. Be very careful - if you get it wrong LAMS won't start.

* Shutdown LAMS / JBOSS.
* Go to the lams.ear directory in jboss.
* Copy the lams-tool-larsrc11.war to somewhere else as a backup, in case you don't make the change correctly and need to rollback the change.
* Unzip lams-tool-lafrum11.war to a temporary directory.
* Edit the file WEB-INF\web.xml.
* Find the entry for "Download Files" and change it to this:
    <security-constraint>
          <web-resource-collection>
            <web-resource-name>Download Files</web-resource-name>
            <url-pattern>/download/</url-pattern>
        </web-resource-collection>
        <auth-constraint>
            <role-name>LEARNER</role-name>
            <role-name>AUTHOR</role-name>
            <role-name>MONITOR</role-name>
            <role-name>TEACHER</role-name>
            <role-name>ADMIN</role-name>
            <role-name>AUTHOR ADMIN</role-name>
            <role-name>SYSADMIN</role-name>
        </auth-constraint>
    </security-constraint>

You will need to add the line <role-name>LEARNER</role-name>

* Rezip up the directory, calling it lams-tool-lafrum11.war. Make sure you don't accidentally get an extra folder in the lams-tool-lafrum11.war file - that will cause an error when JBOSS starts up.
* Start JBOSS/LAMS. The problem should now be fixed.

Fiona

Posted by Fiona Malikoff