Initializing the incorrect API version of controllers (from CE instead of PE) when using the api_key_login(..) method on a RestClientPE object.

[eRJx]

during the call:

with RestClientPE(base_url=url) as rest_client:
rest_client.api_key_login(api_key)

controllers were initialized from CE version instead of PE.

[glglgl-de]

I have noticed a similar behaviour:

when I have a RestClientPE() object and am logged in with a JWT key (client.token_login()), I can do client.get_user_info_by_id(user_id) until the first refresh() call on the object.

This refresh() call seems to call self.__load_configuration() on the base, which in turn calls self.__load_controllers(). These __ methods are mapped to an internal name with a different name, however, so the wrong __load_controllers() is called.

I think the same fixing logic which applies to the original bug in this ticket would apply here as well: call self.__load_controllers() from an overwritten refresh() function in the PE client object.

(IMO this can only be a temporary solution, as first the wrong controllers are created and then overwritten by the correct ones. Maybe it would better to not call the method __load_controllers(), but something without __ at the start.)