Cannot get CPM parameter to pass through to target in the proper formatted syntax required by the target OS. Anyone had luck using netbios domain name standard as login? (i.e. domain_name\account)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Cannot get CPM parameter to pass through to target in the proper formatted syntax required by the target OS. Anyone had luck using netbios domain name standard as login? (i.e. domain_name\account)

L1 Bithead

Have an on-prem ADDS domain service account that is the reconcile account for a local account on a blackbox appliance with a Linux like OS, however the OS requires the netbios\pre-logon 2000 format for the reconcile account to login to it (i.e. domain_name\account) and trying a few variations as shown below all result in the same error shown; as if the CPM or platform does not know how to properly send the values.

 

PRLoginUser=domain_name\account

PRLoginUser="domain_name\account"

PRLoginUser=domain_name\\<extrapass3\username>

PRLoginUser="domain_name\\"<extrapass3\username>

 

(Created file categery 'netbiosname' and added to the platform with value of "domain_name" for this attempt)

PRLoginUser=<extrapass3\netbiosname><extrapass3\username>

PRLoginUser=<extrapass3\netbiosname>\\<extrapass3\username>

 

All result in an error: "ERROR -> c : : d -> aj: Invalid username or secret"

 

I can login successfully to the target manually via an SSH connection with the domain_name\account in question.

 

If I change the 'address' field value of the reconcile account to be "domain_name\account", the reconcile of the target account works but then causes the reconcile account to fail management by the out-of-box platform 'windows domain account'.

 

1 accepted solution

Accepted Solutions

L1 Bithead

I resolved this by using KB#000035637 as a guide and used account groups to achieve the end result I needed.

View solution in original post

3 REPLIES 3

L5 Sessionator

Better use as this:- [email protected]

 

OR

put username field as: username

address field as: domainname.com

L4 Transporter

Hi @Richard Moreno​ 

 

As it seems Sanzu provided an answer for your question, could you kindly share if this solution resolved your issue?

If so, could you please mark the answer as "Select as Best" to help other community members?

 

If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.

 

Thank you,

Liad

L1 Bithead

I resolved this by using KB#000035637 as a guide and used account groups to achieve the end result I needed.

  • 1 accepted solution
  • 123 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!