AppD Archive

LDAP Authenticaton Issues

CommunityUser
Splunk Employee
Splunk Employee

Good Afternoon:

New user, new installation, new qustion.

We've installed AppDynamics and I'm trying to configure LDAP. I'm able to get users and groups, but when I try to authentication it is trying to authenticate me as user@customer1 instead of user@mydomain. If I enter user@mydomain as my account it trys to authenticate me as user@mydomain@customer1.

Everything is local and I've been searching for about 2 hours on how to get rid of the customer1.

Thanks,

Eric

0 Karma

Arun_Dasetty
Super Champion

Hi Eric,

customer1 is the default account name here when user installed controller in single tenant mode controller still uses customer1 as default account, hope that clarifies the product behavior. Also confirm are you are able login fine in UI with the same username imported in ui under users for ldap user referred?

Also confirm the controller UI version as i guess we have some bug where username with special char like @ have issues while login

Can you please send the screenshot from controller UI if the above info. does not help:

- ldap user imported in view (edit mode) from Administrator -> users screen

- values passed in browser controller UI login screen for fields user/password 

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thanks - I need to change the default behavior. It is using customer1 as the authentication domain and not my organizaiton. I'd like to get rid of all references to customer1 if at all possible. We have one account in AppDynamics that we created and that is the administrative account. We are trying to configure LDAP for managing accounts. I am able to get users and groups from the LDAP servers but I cannot get them to authenticate because of the above issue.

Relevant line from log file

[#|2014-08-27T11:54:23.562-0400|WARNING|glassfish3.1.2|com.singularity.ee.controller.auth.AuthRealm|_ThreadID=112;_ThreadName=Thread-6;|Invalid user : <myaccount>@customer1|#]

it should be trying to authenticate <myaccount>@<mydomain>

How do I change the behavior?

Eric

0 Karma

Arun_Dasetty
Super Champion

Hi Eric,

Unfortunately i do not see such provision in controller UI as of now.  Also i see in the screenshot provided the username is blank i used the username is valid string and valid contorller UI user imported. LDAP users imported (assuming ldap user have some valid name like user1, Eric as succh as part of username field value for users imported.

Hope that clarifies the current product behavior. Also please make sure you assign roles to ldap users as stated in docs: http://docs.appdynamics.com/display/PRO39/Configure+Authentication+Using+LDAP#ConfigureAuthenticatio...

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...