Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-12455

If file permissions do not allow Amster to read config files it does not handle it

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 14.0.0, 14.1.0, 14.1.1, 14.5.1, 5.5.1
    • Fix Version/s: None
    • Component/s: Amster
    • Labels:
      None

      Description

      On import if the file permissions for the folder or files containing the exported config do not allow Amster to read the files, Amster does not report an error, but a success - even though no action is taken!

      For example

      1 - Take an export
      2 - Change the file permissions of the exported directories/files e.g. to root:root and chmod 400 for the exported directory
      3 - Try to import
      4 - Result:

      Importing directory <directory location>
      Import completed successfully
      

      Even with the flag

      --failOnError true
      

      5. I have only tested for import but I suspect this affects all Amster operations

      6. Note if the import directory is not present then an error is returned:

      Path does not exist: <path>
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              shokard Darinder Shokar
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated: