Skip to content

removing SAML conf has residual error #1186

Description

@revansx

Environment

  • RHEL7
  • Meza 31.8.0

Issue summary

After removing SAML configuration from public and secret yml pages and performing a successful redeploy, landing page fails with residual SAML error.

Issue details

  1. Performed a Fresh install of Meza on a new server
  2. Everything is verified to work well.
    --- landing page works
    --- demo wiki works)
  3. First customization activity was to edit the public.yml and secret.yml with the SAML configuration for my environment.
  4. Deploy fails because my organization has not yet set-up the remote SAML agent
  5. Reverted public.yml and secret.yml back to their non-SAML revision (No SAML)
  6. Deploy is successful
    --- Demo Wiki works
    --- Landing page fails (Error 500)

Apache Error logs contains:

[Wed Jun 05 14:52:28.728999 2019] [php7:warn] [pid 3402] [client 127.0.0.1:40248] PHP Warning: require_once(/opt/htdocs/NonMediaWikiSimpleSamlAuth.php): failed to open stream: No such file or directory in /opt/htdocs/index.php on line 5

[Wed Jun 05 14:52:28.729080 2019] [php7:error] [pid 3402] [client 127.0.0.1:40248] PHP Fatal error: require_once(): Failed opening required '/opt/htdocs/NonMediaWikiSimpleSamlAuth.php' (include_path='.:/usr/share/pear:/usr/share/php') in /opt/htdocs/index.php on line 5

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions