Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-18039 META: Security overview report STABLE
  3. MDL-18258

Admins with no clue when "Incorrectly defined default course roles detected!"

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.9.4
    • Fix Version/s: 1.9.5
    • Component/s: Administration
    • Labels:
      None
    • Affected Branches:
      MOODLE_19_STABLE
    • Fixed Branches:
      MOODLE_19_STABLE

      Description

      We are experincing difficulties on shooting the problem reported by Security Report. The message is:

      Default roles (courses) Critical Incorrectly defined default course roles detected!

      and the explanations are:

      • Risky capabilities detected in context.
      • Risky capabilities detected in context.
      • Risky capabilities detected in context.
      • Unsupported legacy type detected.

      Clicking on "context" where risky capabilities are found, Admins are sent respectively to the role details of Course creator, Student and Teacher. Resetting the default of each role does not solve the Security report Issue

      About "Unsupported Legacy type detected", there are no legacy type different from the standard, nor there are clues where the Unsupported legacy type is found

        Gliffy Diagrams

          Activity

          Hide
          skodak Petr Skoda added a comment -

          Resetting will not help because those problem are in role overrides - working on some improvements...

          Show
          skodak Petr Skoda added a comment - Resetting will not help because those problem are in role overrides - working on some improvements...
          Hide
          skodak Petr Skoda added a comment -

          oh, you need to have a look at risks before resetting to defaults!
          There might be problems in contrib modules which may have risky default caps or incorrect definition of risks.

          Show
          skodak Petr Skoda added a comment - oh, you need to have a look at risks before resetting to defaults! There might be problems in contrib modules which may have risky default caps or incorrect definition of risks.
          Hide
          andreabix Andrea Bicciolo added a comment -

          Thanks Petr. And what about the Unsupported Leagcy Type?

          Show
          andreabix Andrea Bicciolo added a comment - Thanks Petr. And what about the Unsupported Leagcy Type?
          Hide
          skodak Petr Skoda added a comment -

          well, that was a bug :-O

          now fixed in cvs, this report should also give better hints now, please update and retry

          Show
          skodak Petr Skoda added a comment - well, that was a bug :-O now fixed in cvs, this report should also give better hints now, please update and retry
          Hide
          nicolasconnault Nicolas Connault added a comment -

          Confirmed as fixed. Thanks Petr.

          Show
          nicolasconnault Nicolas Connault added a comment - Confirmed as fixed. Thanks Petr.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                13/May/09