Log on to e FQDN

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

Log on to e FQDN

L3 Networker

Hello

 

Two questions:

 

1) When we onboard a local account, we put the FQDN of the target server in the "address" field and we also put it in the "log on to" field. Why isn't the "address" field used to make a connection?

 

 

2) In my lab I made this configuration using FQDN in both fields and it worked fine.

 

In another environment, I replicated this configuration and access did not work. Starts connection and gives username and password error.

We removed the FQDN from the "log on to" field, leaving only the hostname and it worked, very WEIRD. Has anyone ever seen something like this?

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @Tiago Toledo​ 

 

The ‘address’ filed is used to specify the target host name whereas ‘logon to’ field is used to specify the name of the domain where target account will be used.

 

To answer your first question:

 

CyberArk uses the “log on to” field to direct the authentication request to the correct context, ensuring that the username and password are validated against the intended domain. This allows for more flexible configurations where the address might differ from the authentication context, especially in complex network environment.

 

To answer your second question:

 

In a controlled lab environment, DNS resolution and domain relationships are might be straightforward. The FQDN might correctly resolve and authenticate without issues.

 

There could be few causes here

 

Depending on the LAB setup,

 

  • DNS resolution might differ. The system might interpret the FQDN differently in the “log on to” field, leading to authentication error.
  • The Active Directory structures can cause variations in how authentication requests are processed.

 

Hope it helps !

 

View solution in original post

2 REPLIES 2

L7 Applicator

Hi @Tiago Toledo​ 

 

The ‘address’ filed is used to specify the target host name whereas ‘logon to’ field is used to specify the name of the domain where target account will be used.

 

To answer your first question:

 

CyberArk uses the “log on to” field to direct the authentication request to the correct context, ensuring that the username and password are validated against the intended domain. This allows for more flexible configurations where the address might differ from the authentication context, especially in complex network environment.

 

To answer your second question:

 

In a controlled lab environment, DNS resolution and domain relationships are might be straightforward. The FQDN might correctly resolve and authenticate without issues.

 

There could be few causes here

 

Depending on the LAB setup,

 

  • DNS resolution might differ. The system might interpret the FQDN differently in the “log on to” field, leading to authentication error.
  • The Active Directory structures can cause variations in how authentication requests are processed.

 

Hope it helps !

 

Thank you for answering.

  • 1 accepted solution
  • 565 Views
  • 2 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!