Users cannot log into their custom tenant after restoring indexes #263

Hi everyone!
We use docker-compose for deploy our cluster, product versions: amazon/opendistro-for-elasticsearch:1.13.1 and amazon/opendistro-for-elasticsearch-kibana:1.13.1.
We take a snapshot of the indexes on the working cluster (3 nodes) and transfer them to a similar new cluster (3 nodes), at the same time we take a snapshot of the opendistro_security plugin’s configuration files:
# ./securityadmin.sh -backup /mnt/path/ -icl -nhnv -cacert /usr/share/elasticsearch/config/root-ca.pem -cert /usr/share/elasticsearch/config/admin.pem -key /usr/share/elasticsearch/config/admin.key
We start a new cluster with opendistro_security.disabled: true , setup snapshot repository, restore the indexes with:

  "ignore_unavailable": true,
  "include_global_state": true,
  "include_aliases": true

enable the opendistro_security plugin, restart the odfe cluster (by mounting the following directories into containers like all certs from old cluster, all yml files from securityconfig directory) and start kibana. Example for odfe-node01:

    volumes:
       ....
      - ./certs/new/root-ca.pem:/usr/share/elasticsearch/config/root-ca.pem
      - ./certs/new/odfe-node-prod-odfe01.key:/usr/share/elasticsearch/config/o4n01.key
      - ./certs/new/odfe-node-prod-odfe01.pem:/usr/share/elasticsearch/config/o4n01.pem
      - ./certs/new/odfe-node-prod-odfe01_http.key:/usr/share/elasticsearch/config/o4n01_http.key
      - ./certs/new/odfe-node-prod-odfe01_http.pem:/usr/share/elasticsearch/config/o4n01_http.pem
      - ./certs/new/admin.pem:/usr/share/elasticsearch/config/admin.pem
      - ./certs/new/admin.key:/usr/share/elasticsearch/config/admin.key
      - ./elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml
      - ./securityconfig:/usr/share/elasticsearch/plugins/opendistro_security/securityconfig/

    volumes:
      - ./certs/new/root-ca.pem:/usr/share/kibana/config/root-ca.pem
      - ./certs/new/prod-odfe01-kibana_http.key:/usr/share/kibana/config/o4n01-kibana_http.key
      - ./certs/new/prod-odfe01-kibana_http.pem:/usr/share/kibana/config/o4n01-kibana_http.pem
      - ./custom-kibana.yml:/usr/share/kibana/config/kibana.yml

After that I execute the command to apply the new settings:
# ./securityadmin.sh -cd /usr/share/elasticsearch/plugins/opendistro_security/securityconfig/ -icl -nhnv -cert /usr/share/elasticsearch/config/admin.pem -cacert /usr/share/elasticsearch/config/root-ca.pem -key /usr/share/elasticsearch/config/admin.key
No errors, cluster have “green” status, i login like admin and all the settings made on the old cluster are identical in the new cluster, but when I log in as a user in kibana ui, user does not have any custom tenants for select.
At what step in restoring indexes from one cluster to another did I make a mistake?
Thanks for any help.