3.2.3 2.5.x向2.6.x升级

iTop的版本2.6.0与先前的2.x版本完全向后兼容,但是此版本引入了许多重大更改。

本文档重点介绍了将iTop迁移到版本时可能发生的问题。

  • 要重点关注新功能,请检查什么是新的 
  • 有关更改的详尽列表,请检查变更日志 

用户上的影响度

用户存储的URL

为了解决安全的弱点,我们必须对变更进行编码,方法是在URL中对过滤器参数进行编码。结果,用户可能已经为iTop URL加了书签,在更新到iTop 2.6后可能不再起作用。

带有唯一性规则的对象版本(人)

由于添加了唯一性规则,如果您的Persons在相同的组织下,并且具有相同的员工ID,则在解决员工ID的冲突之前,无法修改这些Person。

品牌和模型上已添加了唯一性规则,它们应具有唯一的名称。您的iTop中很可能没有重复项。

升级前检查

对于开发人员

2.6.2版本开始,对于大多数操作,现在仅将对pagesajax.render.php端点的调用限制为后台办公室UI。请调整您将创建的任何门户扩展,并使用自己的终结点。

配置参数可用于禁用此保护,请在配置文件中添加以下内容:

'disable_attachments_download_legacy_portal' => false,

不支援MySQL 8

另外,您可能已经在版本2.6的MySQL 8上运行了iTop,升级不再可能在此数据库上安装iTop。我们计划使用iTop2.7消除了此限制。

数据模型变更

如果您已在ITSM设计器或Windows XP的扩展中强制使用_delta =“ define”

//class[@id="Change"]/lifecycle/states/state[@id="new"]/flags/attribute[@id="caller_id"] 

change 变更可以是变更中的任何子类。

您需要变更或向Combodo要求变更,将其输入_delta =“ force”

原有门户已弃用

如果尚未完成,请在安装过程中激活增强门户进行更换。

加密变更

关于PHP最近对mcrypt的支持下降,我们更新了处理加密的方式。检查一下加密数据 确保不会丢失对先前加密的数据的访问权限。

如果您将升级设为2.6,

  • 建一些加密的数据(例如,带有密码的本地iTop用户)
  • 2.6之前还原为版本

然后:

  • 在2.6中创建的加密数据将不再可读
  • 例如创建的用户将无法使用登录名

备份参数变更

如果将check_backup.php与参数check_ticket_itop一起使用,它将损坏!

由于安全的原因,不应再使用“ check_ticket_itop”参数。

  • 现在,此URL必须存储在配置文件中模块参数的“  itop_backup_incident”键下。
  • 在iTop 2.5.2中,有一个参数itop_root,现在是itop_backup_incident
  • 调用check_backup.php时,从cron中使用的“参数文件”中删除参数check_ticket_itop。
  • 并将先前位于check_ticket_itop中的价值放入配置文件itop_backup_incident

对于开发人员

不推荐使用的功能

在Config对象中,以下方法已在2.5中弃用,并将在2.7中删除:

  • GetDBHost
  • GetDBName
  • GetDBSubname
  • GetDBCharacterSet
  • GetDBCollat​​ion
  • GetDBUser
  • GetDBPwd

这些方法应分别调用通用的Config :: Get方法,并使用适当的变量名称:

  • db_host
  • db_name
  • db_subname
  • db_character_set
  • db_collat​​ion
  • db_user
  • db_pwd

原创链接:https://www.itophub.io/wiki/page?id=2_7_0%3Ainstall%3A250_to_260_migration_notes


2.5.x to 2.6.0 Migration Notes

The version 2.6.0 of iTop is fully backward compatible with the previous 2.x versions, however this version introduces quite a few significative changes.

This document highlights issues which can occur while migrating your iTop to this version.

  • For a focus on new features check What's New

  • For an exhaustive list of changes check the Change Log

Impact on users

User stored URLs

In order to fix a security weakness, we had to change the way filter parameter was encoded in URL. As a result users may have bookmarked iTop URLs which may no more work after updating to iTop 2.6.

Edition of object with Uniqueness rules (Person)

As a uniqueness rule has been added, if you have Persons under the same Organization, with the same employee id, then modification of those Person won't be possible until that collision of employee id is fixed.

Uniqueness rules have been added on Brand and Model, which are expected to have a unique name. Most probably no duplicates exist in your iTop.

To check before upgrading

For developers

From 2.6.2 Calls to the /pages/ajax.render.php endpoint are now restricted to the backoffice UI for most of the operations. Please adjust any portal extension you would have created and use your own endpoint.

A configuration parameter is available to disable this protection, add the following to the configuration file:

'disable_attachments_download_legacy_portal' => false,

MySQL 8 not supported

Also you might have an iTop running on MySQL 8, with version 2.6 it's no more possible to upgrade or install iTop on this database. We plan to remove this limitation with iTop2.7.

Datamodel changes

If you have forced a _delta=“define” in the ITSM Designer or in an Extension on

//class[@id="Change"]/lifecycle/states/state[@id="new"]/flags/attribute[@id="caller_id"] 

change can be any sub-class of Change.

You will need to change or ask Combodo to change for you this into _delta=“force”

Legacy Portal is deprecated

If not done already, activate the Enhanced Portal during the Setup to replace it.

Encryption changes

Regarding recent mcrypt support drop from PHP, we updated the way encryption is handled. Check Encrypt Data to be sure you won't loose access to your previously encrypted data.

If you upgrade to 2.6,

  • create some encrypted data (for eg. a local iTop user with password)

  • revert to a version before 2.6

Then:

  • the encrypted data created in 2.6 won't be readable anymore

  • for eg. the created users won't be able to login

Backup parameter change

If you use check_backup.php with this parameter check_ticket_itop, it will break!

For security reasons, the “check_ticket_itop” parameter should not be used anymore.

  • This URL must now be stored in the module parameters, in the config file, under the “itop_backup_incident” key.

  • In iTop 2.5.2 there was a param itop_root which is now itop_backup_incident

  • Remove the param check_ticket_itop from the “param file” used in your cron when calling check_backup.php.

  • and put the value previously located in check_ticket_itop, into the Configuration file itop_backup_incident parameter

For Developers

Deprecated functions

In the Config object, the following methods were deprecated in 2.5 and will be removed in 2.7 :

  • GetDBHost

  • GetDBName

  • GetDBSubname

  • GetDBCharacterSet

  • GetDBCollation

  • GetDBUser

  • GetDBPwd

Those methods should be replaced by a call to the generic Config::Get method, with the appropriate variable name, respectively :

  • db_host

  • db_name

  • db_subname

  • db_character_set

  • db_collation

  • db_user

  • db_pwd

标签:
由 superadmin 在 2020/08/27, 15:57 创建
    

需要帮助?

如果您需要有关XWiki的帮助,可以联系:

深圳市艾拓先锋企业管理咨询有限公司