Changing Kerberos Principal from nothing to "---" breaks AD form
Description
Problem/Justification
None
Impact
None
Activity
Show:
Bug Clerk February 27, 2022 at 6:51 PM
Bug Clerk February 24, 2022 at 5:17 PM
Andrew Walker February 11, 2022 at 3:26 AM
If you're joined to AD, you also shouldn't be changing this. We don't store credentials for privileged accounts on the NAS. Once you join AD, we clear the bind credentials and use the kerberos keytab for any necessary authentication. Deselecting both is not permitted. I understand there is possibly a webui issue here, but I also think you might be barking up the wrong tree with what you're doing.
Zack February 10, 2022 at 11:38 PM
Sorry, I was unclear. It's an AD DS server; I just said LDAP instead of DS
Andrew Walker February 10, 2022 at 4:04 PM
Why are you setting up LDAP with AD configured? You should leave the AD domain first.
Complete
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Alex KarpovReporter
ZackLabels
Time remaining
0m
Components
Fix versions
Affects versions
Priority
LowKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created February 10, 2022 at 3:53 PM
Updated July 6, 2022 at 8:59 PM
Resolved February 28, 2022 at 8:32 AM
When setting up AD on 22.02-RC.2, I changed the Kerberos Pincipal under Advanced Settings from its default nothing value to "---", which caused Domain Account Name and Domain Account Password to dissapear until I closed and reopened the form.