Task #3196
Change actual setup workflow to something more friendly
Status: | New | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | 2.0 |
Description
The idea is to simplify the way connections setup between the 2 glpi instances are made.
I'd like to propose is the following 2 workflows:
Slave -> Master¶
- On the master, we first create a webservice connection with a special user.
This user will only have access to a specific entity to synchronize with. - Then the slave identify itself to the master server with its token and the user
previously created. - The master will create automatically the connection to the slave, if it doesn't
exist, or update it. - The slave is automatically configured to synchronize its root entity to the entity
restricted by the master's webservice user. - Finally, the administrator on the master can choose to deploy or recover data.
Master -> Slave¶
- On the master, we create a connection to the slave and we configure which entity to
synchronize on the slave. - We initiate the identification from the master to the slave.
- On the slave, this will create/update the connection to master and configure
automatically the destination entity. - Finally, the administrator on the master can choose to deploy or recover data.
Notes¶
- WebService's login/password configurations may not be allowed to be sent clear
between the 2 servers. We can send this through https else slave or master will have
to setup those separately.
Comments are more than welcome ;)
History
#1 Updated by walid almost 10 years ago
- Target version changed from 1.0 to 2.0