Thank you Richard. But don't we need an active account to be able to access the dmcli?  With no user licenses assigned, how am I supposed to authenticate to add the APLS user to Dimensions with dmpasswd utility?

Thanks

Grant

D'oh, my mistake was trying to use the dmcli, worked with cmd.  Sometimes it takes someone not pointing out what your wrong to actually see what your doing wrong.

Let me know how you get on and if you need any more help 

Thank you Richard!  Once I add the admin user, should I be able to log in to Dimensions admin console with that Admin user?

That admin user is specific to APLS. You won't be able to login to Dimensions CM as that user. 

I would recommend restarting the Dimensions CM listener to make sure it picks up the new password you've registered. The registry.dat file is read when the listener is first started.

You should then be able to connect to Dimensions CM as the standard admin user you specified during install normally dmsys (or any user you've used with CM before) as long as you've added a valid license to APLS. 

Thank you.  For some weird reason, I've never been able to authenticate to Dimensions CM using the dmsys account.  I use it to create new projects, but that's the only place the auth works.  Perhaps this is due to our using AD for auth?  Note, I inherited this thing a few years back, and my main admin responsibilities lie with Splunk, so I've not dug too deeply into the inner guts of Dimensions. 

Attempting to login using my AD account returns this error:

I mentioned earlier, is APLS installed on the same server as Dimensions CM? If it is you can avoid the need to install a valid certificate by using the following in the server dm.cfg file:

DM_LICENSE https://localhost:5814/autopass

Rather than using the 'real' hostname as that would require a valid certificate to have been installed. As with any change to dm.cfg you will need to restart the Dimensions CM listener. 

Okay, yes, I had the hostname being used for that setting.  Updated, restart of DM listener, attempted login using my personal admin account:

Log In Failure: Client named user identifier is invalid for named feature '101450:1' checkout request. Could not connect to database hudtest@dmtest. Please check DB name and DB connection, and that the remote listener is running.

Backtrack for a sec to the dmsys account, in order to log in to Dimensions with that account, is there a setting in the dm.cfg that would allow for me to login with that as a local account while also maintaining LDAP auth?

On the error, had you installed a valid license in APLS? Can you try a second time? I have seen cases of the very first connect attempt failing but subsequent attempts work (in the background that initial attempt registers the product in APLS which is why that happens). 

Does dmsys exist only as a local OS user? Unfortunately once you configure Dimensions CM to authenticate through LDAP it will use that for all users. 

Unfortunately yes, the dmsys user only exists as local os user.  For the license, yes as well, it has been installed in APLS.  Still no dice with the auth though.

The License type is Perpetual, with 5 licenses set aside for our test environment.  Capacity unit of measure is "Named User".

Perhaps it's easier if we get on a call tomorrow and work through this? I'll drop you an email Grant. It's late here in the UK now so hopefully tomorrow is ok

Perhaps it's easier if we get on a call tomorrow and work through this? I'll drop you an email Grant. It's late here in the UK now so hopefully tomorrow is ok

That works perfect.  Thank you so much Richard, you have been immensely helpful!  Can we set up a webex perhaps?