Hello,

The matter is that Dimensions CM is not performing the authentication itself. It "delegates" that to one of authentication methods (say, local OS authentication, LDAP, PAM). So, you'd need the corresponding userID to be also present in that external authentication system, where also credentials are validated.

More information can be found in the Administration Guide PDF, the chapter "Configuring Centralized Network Authentication".

Hello Alex,

Thank you for your reply ,but there is still something wrong  when i try to check the network authentication in the dm.cfg file, i found the file as below:

I don't know how it works with the config in the red frame above.

when i want to  upload the whole file ,it doesn't work ,maybe it's too large.

I'm looking forward to your reply ,thanks a lot!

Hello,

Since the variable "DM_AUTH_TYPE_DBS" is commented out, the Native Authentication type should be used.

If that is Linux server - the authentication is likely performed via the operating system users.

If that is Windows server - through one of domains (user's, primary domain of server or defined through DM_LOGON_DOMAIN dm.cfg variable).

Detailed info on the Native Authentication can be found in the Architecture and Optimization Guide (page 14).

So, you need to create a corresponding user either in the operating system of server running Dimensions CM or (what is more often used) in the domain the server is belonging to.

Hello Alex,

Thank you for your help, you're right ,that's the key point , the issue has been solved and we can now work with it well ,thanks again!