Search the FirstSpirit Knowledge Base
I wrote a Service modul
public class PimImportServiceImpl implements PimImportService,
de.espirit.firstspirit.module.Service<PimImportService> {
...
}
that imports data into a project opening a connection using the Connection Manager:
Connection connection = ConnectionManager.getConnection(host, port, ConnectionManager.HTTP_MODE,login, password);
to write data into the database of a FirstSpirit project.
The import of the data is triggered by a user that is already logged into the CMS using a beanshell script. I am looking for a way to avoid having a user to provide their password again as needed by the ConnectionManager interface.
Is there another way to handle that?
The interface Service has an "init" method which is called by FirstSpirit, providing a ServerEnvironment instanance. This in turn has a method "getConnection()". So there is no need to create a connection by yourself.
The interface Service has an "init" method which is called by FirstSpirit, providing a ServerEnvironment instanance. This in turn has a method "getConnection()". So there is no need to create a connection by yourself.
Hi Peter,
but what if you need administrative rights - for example, to manipulate the FirstSpirit ProjectStorage without having logged in as a project or super admin?
Then you need to create a dedicated FirstSpirit connection providing:
- user name
- password
credential information on the client side.
If you wanna change the Super-Admin password later - you have to identify all client applications and change it there
Thats really bad. How might this be solved? Because, retrieving the Admin-Password by API-calls is not possible as well (due to security reasons).
We already discussed a solution here: Centralizing Admin user information