Getting the identity parameters in a Custom DFS Service

Hello all

we have developed a DFS custom service which uses Enterprise Content Services.

Our DFS custom service is accesed by an external web application using the DFS productivity layer, that is the client sets the context and instanciates the custom service by using his own identity (user, password, repository).

The problem is that our custom service has to create a new context to user the Enterprise Content Services and we would like to use the same identity of the initial application...

Briefly... how can we get the identity that sets the external web application in our custom service to use the same user/password/repository to instanciate the Enterprise Content Services???

Thank you

Find more posts tagged with

Comments

zhou_simonq

Does "Enterprise Content Services" mean DFS?

If I'm not wrong, the external web application consumes your custom services, which consume DFS. If you want to use the same user/password/repository information set in external web application for custom services to consume DFS, you can get the user/password/repository and construct a RepositoryIdentity instance and add it to the ServiceContext instance. It's just like a normal DFS client to access DFS services.

- simon

rpdiaz

Yes, Enterprise Content Services mean the basic DFS services (core, bpm, search, ...)

We want to make what you say (to create a new ServiceContext instance), but our question is how to get this parametets (user, password, repository) from the initial client in the custom service code...

Thank you

rpdiaz

Hi,

now we are trying to do it in 2 different ways:

1) by adding a constructor method in the DFS custom service class which sets the context and instanciates the Enterprise Content Services:

public CustomService(String repositoryName, String userName, String password, boolean remoteMode)throws ServiceInvocationException{super(repositoryName, userName, password);setContext(userName,password);setService();}protected void setContext(String userName, String password){ContextFactory contextFactory = ContextFactory.getInstance();serviceContext = contextFactory.newContext();RepositoryIdentity repoId =new RepositoryIdentity();repoId.setRepositoryName(defaultRepositoryName);repoId.setUserName(userName);repoId.setPassword(password);serviceContext.addIdentity(repoId);ContentTransferProfile contentTransferProfile =new ContentTransferProfile();contentTransferProfile.setTransferMode(ContentTransferMode.UCF);serviceContext.setProfile(contentTransferProfile);serviceContext.setRuntimeProperty(IServiceContext.USER_TRANSACTION_HINT, IServiceContext.TRANSACTION_REQUIRED);}private void setService(){ServiceFactory serviceFactory = ServiceFactory.getInstance();try{if(remoteMode){objectService = serviceFactory.getRemoteService(IObjectService.class, serviceContext,"core","http://localhost:8888/services");queryService = serviceFactory.getRemoteService(IQueryService.class, serviceContext,"core","http://localhost:8888/services");workflowService = serviceFactory.getRemoteService(IWorkflowService.class, serviceContext,"bpm","http://localhost:8888/services");}else{objectService = serviceFactory.getLocalService(IObjectService.class,serviceContext);queryService = serviceFactory.getLocalService(IQueryService.class,serviceContext);workflowService = serviceFactory.getLocalService(IWorkflowService.class,serviceContext);}}catch (ServiceInvocationException e){e.printStackTrace();throw new RuntimeException(e);}}

The problem of this option is that the customservice-remote.jar does not includes the implementation class so the client can not user the constructor method...

Another option is to give the clients the customservice.jar which includes the implementation classes, but we do not know if it is convenient.

2) By adding a new setContext method in the DFS Service (instead of doing it in the constructor method).

publicBut it is not very nice because it depends that the client sets the context before calling a method...Any idea would be appreciated Thank you void setContext (String repositoryName, String userName, String password) throws ServiceInvocationException{setDefaultRepositoryName(repositoryName);setUserName(userName);setPassword(password);setContext(userName,password);setService();}

zhou_simonq

When the client consume your custom services, there will be SOAP requests. You can add some authentication info in the header of the requests. Also, you can take advantage of DFS productivity to set the SOAP header, so you don't need to operate SOAP requests manually.

As alternative, you can use AD to authenticate user, etc.

- simon

zhou_simonq

There is a piece of code as attachment here:

https://community.emc.com/message/452902#452902

i'm not sure whether it can help you.

- simon

rpdiaz

Hi Simon

in the java example code, the service has a constructor to pass arguments user, password and repository, but this is only possible when you are using DFS productivity layer and the client has the executable class... not just the remote access...

How can you use DFS productivity layer to set the header of the SOAP message?

What is AD to authenticate user?

Thank you very much for your help!!

zhou_simonq

I guess that you want to use SSO (single sign on). Currently DFS supports SiteMinder and Netegrity as the authentication server, if I'm not wrong. There is a section in DFS dev guide about SSO support.

- simon