nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DFS hard code parameters

ssmirnov

In DFS example we can find a project HelloWorldService. Considering client-remote - HelloWorldClient.java we set a connection parameters to docbase:

.................

String moduleName = "example";

String contextRoot = "http://192.168.12.90:9080/services/";

String repository = "docbasename";

String user = "superuser";

String password = "password";

ContextFactory contextFactory = ContextFactory.getInstance();

IServiceContext context = contextFactory.newContext();

RepositoryIdentity repoId = new RepositoryIdentity();

repoId.setRepositoryName(repository);

repoId.setUserName(user);

repoId.setPassword(password);

context.addIdentity(repoId);

.....

Connection establish successfully, but isn't a hard code to set parameters in my client application? Have any other way to do it without hardcoding?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Button

Accepted answers

aflowers001

Getting a username & password & repository from a client application will be specific to that client application and will be based on code/configuration you write.

If you are not using the credentials of the currently logged on user then you would need to store the required credentials in whatever configuration mechanism, or application database, you have at hand.

This is not a DFS issue rather it is a client applicacation specific issue you have to deal with.

All comments

aflowers001

Yes.

Take a look at the dfs-client.xml file in the documentation and the examples in DFS SDK.

ssmirnov

I now about that xml. There we can put in it just a module name, host, protocol, port and context root.

My question was in connection parameter(repository name, user name, password).

aflowers001

These come from the client.

If it's a web application you will have a username, perhaps a password and you will know the repository.

If you wish to hard code the access the client application can do this using whatever technology it uses.

If you wish to use SSO or somesuch then if you take a look at the DFS guides they cover this.

If this is not what you are after can you please expand upon what it is you are trying to accomplish?

ssmirnov

Yes, your right, Its web application. Ok, docbase name, user name I can get it, but how I can get password for my super user? Can your lead some example code?

aflowers001

Hi,

Not sure what you're asking for.

If you're asking how do you get the password of the user logged in to your web site you will need to consult your web framework documentation for that.

If you're after the password for a know 'superuser' then that will have to be placed into the application configuration files/settings.

What super user password are you after?, and why?

ssmirnov

Ok, for example, I'am create service context like this:

............................................

public void setContext(String repository, String userName,String password)

{

ContextFactory contextFactory = ContextFactory.getInstance();

serviceContext = contextFactory.newContext();

RepositoryIdentity repoId = new RepositoryIdentity();

repoId.setRepositoryName(repository);

repoId.setUserName(userName);

repoId.setPassword(password);

serviceContext.addIdentity(repoId);

}

.................................

and for example in a signature of method setContext I'am put my hardcode params: repository - repo, userName - dmadmin, password - qwerty. The question was in that, How can I get user name(not from session logged) and his password. Maybe put this information separately in xml file?

All this call from application server.

aflowers001

Getting a username & password & repository from a client application will be specific to that client application and will be based on code/configuration you write.

This is not a DFS issue rather it is a client applicacation specific issue you have to deal with.