Method for setting up a secure end-to-end communication between a user terminal / a context broker server and a connected object, characterised in that it uses a first server called the access authorisation server, and a second server called the production server, the user terminal communicating with the access authorisation server through a first secure communication and the production server communicating with the access authorisation server through a second secure communication, the access authorisation server hosting a first database containing information to authenticate the different users and to manage their access rights to the different connected objects, the production server hosting a second database containing identifiers of the connected objects and having an initial private and public key pair ( K init, Q init), characterised in that it includes the following steps: (a) following a user request containing the identifier of the connected object, request from the access authorisation server to the production server to verify that this identifier is valid; (b) when the connected object is initialised, identification and authentication of the connected object by the production server, using a first message ( M 1) containing the identifier of the connected objected and the same identifier, encrypted by the initial public key ( Q init); (c) if the connected object is successfully authenticated, the access authorisation server generates a second message ( M 2) containing the parameters of a cryptosystem, the second message being previously signed by the production server, the message and its signature (sgn( M 2)) being transmitted to the connected object; (d) the connected object generates a private and public access key pair ( K F,Q F), starting from the parameters of the cryptosystem, to set up a third secure communication between the access authorisation server and the connected object; (e) set up a secure communication between the user terminal, resp. the context broker server, and the connected object by means of a symmetric key distributed by the access authorisation server, firstly to the user terminal through the first secure communication, resp. the broker server, through a fourth secure communication, and secondly to the connected object through the third secure communication. (a) following a user request containing the identifier of the connected object, request from the access authorisation server to the production server to verify that this identifier is valid; (b) when the connected object is initialised, identification and authentication of the connected object by the production server, using a first message ( M 1) containing the identifier of the connected objected and the same identifier, encrypted by the initial public key ( Q init); (c) if the connected object is successfully authenticated, the access authorisation server generates a second message ( M 2) containing the parameters of a cryptosystem, the second message being previously signed by the production server, the message and its signature (sgn( M 2)) being transmitted to the connected object; (d) the connected object generates a private and public access key pair ( K F,Q F), starting from the parameters of the cryptosystem, to set up a third secure communication between the access authorisation server and the connected object; (e) set up a secure communication between the user terminal, resp. the context broker server, and the connected object by means of a symmetric key distributed by the access authorisation server, firstly to the user terminal through the first secure communication, resp. the broker server, through a fourth secure communication, and secondly to the connected object through the third secure communication.