How to resolve Recoverable fatal error: Object of class Drupal\Core\Link could not be converted to string in Drupal\Component\Utility\Xss::filter?

How to resolve Recoverable fatal error: Object of class Drupal\Core\Link could not be converted to string in Drupal\Component\Utility\Xss::filter?

我正在按照 How to Configure SimpleSAMLphp for Drupal 8 on Acquia 说明进行操作。我在底部,它说 "SimpleSAMLphp_auth module settings. I personally recommend to store configuration for SimpleSAMLphp_auth module settings in settings.php." 一旦我将他在该代码片段中的代码复制到我的 settings.php 文件(粘贴在底部)并将其推送到 Acquia,我得到了这个当我尝试通过 dev.mysite.com/user url.

登录时出错

网站遇到意外错误。请稍后再试。可恢复的致命错误:class Drupal\Core\Link 的对象无法在 Drupal\Component\Utility\Xss::filter() 中转换为字符串(core/lib/Drupal/Component/Utility/Xss.php 的第 67 行)。

下面显示的代码是我 settings.php 文件中的代码。

$config['simplesamlphp_auth.settings'] = [
  // Basic settings.
  'activate'                => TRUE, // Enable or Disable SAML login.
  'auth_source'             => 'default-sp',
  'login_link_display_name' => 'Login with your SSO account',
  'register_users'          => TRUE,
  'debug'                   => FALSE,
  // Local authentication.
  'allow' => [
    'default_login'         => TRUE,
    'set_drupal_pwd'        => TRUE,
    'default_login_users'   => '',
    'default_login_roles'   => [
      'authenticated' => FALSE,
      'administrator' => 'administrator',
    ],
  ],
  'logout_goto_url'         => '',
  // User info and syncing.
  // `unique_id` is specified in Transient format, otherwise this should be `UPN`
  // Please talk to your SSO adminsitrators about which format you should be using.
  'unique_id'               => 'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn', 
  'user_name'               => 'uid',
  'mail_attr'               => 'mail',
  'sync' => [
    'mail'      => FALSE,
    'user_name' => FALSE,
  ],
];

如果我在我的 setings.php 文件中注释掉这整块代码,那么我就可以登录到我的 dev.mysite.com/user drupal 站点。我不清楚的另一件事是,我是先 "Check Activate authentication via SimpleSAMLphp option" 然后将代码片段复制到我的 settings.php 文件并推送到 Acquia 还是相反?

非常感谢任何帮助。

更新到 8.x-3.0-rc2 版本似乎解决了上述错误。但是,看起来它引入了另一个问题,"This site can't be reached" 并将站点重定向到端口 80。