Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Can't login with local accounts...

I have a user that is not a part of my company and is not in our Active Directory, but want to give them access to the ONE node of their's we monitor (site to site VPN tunnel). When I create a local user in Orion I cannot get that account to authenticate, keeps repeating the dialog box. I use Windows integrated logins with accounts that are formatted in "domain\user", and have tried specifying "servername/localuser" when logging in...no luck.

How do I get this local Orion user to authenticate properly?

Find more posts tagged with

Accepted answers

All comments

chris.schear

...I'll open a support ticket.

vhcato

Chris,

I haven't personally seen any issues with using local accounts with 8.5.1 SP1. We also use domain authentication for all of our users who have special privs, but we have other accounts used for general access by our various business units that are authenticated locally on the NPM server. The users authenticating locally normally just click on a link on our login page that has the creds imbedded, but they can also use the input boxes as well.

chris.schear

Support has stated...

Update for Case #26951 - "Can't login with local accounts"
Chris,
Thank you for contacting SolarWinds. There is not going to be a way to choose between Windows Authentication or regular access, which is basically what you are wanting. It has to be one or the other. If this customer needs to have access, the only way at this time would be to either remove the Windows Authentication or get him and account on the domain, which I realize is not a good idea. I would normally recommend directlink as well, but with the ASP.Net conversion we are working on an issue with Directlink that will auto-login any person who tries to access the website.
Regards,
SolarWinds Tier III Support

vhcato

Weeeeell now... Isn't that interesting..?

It works for us, but we also have some custom stuff going on. We modified "Login.aspx" such that anyone who doesn't have a domain account defined on the NPM server will be presented with a login page with various options. On this page, we have links to various views; each of which has the actual login creds imbedded in the URL. Each of these accounts has appropriate account limitations and view assignments such that they only see elements of interest to them. Naturally, some might consider this a security risk, but we have no concerns over providing this info to anyone in our company. From this page, one can also enter local or domain creds into the input boxes and it seems to work for us.

Attached is a zip of the two files used to facilitate this. One is our "Login.aspx", and the other is an "include" file (Links_Include.txt) which has the remainder of the links that are represented on the page. The separate include file is left over from our 7.8.5 instance with the wireless module installed, wherein there were two login.asp files, depending on whether you were hitting the site initially, or were in there previously and clicked on "logout". This file was referenced from both login.asp files, but could be merged with the login.aspx file now.

aLTeReGo

I've had no troubles creating "local" accounts in addition to Active Directory accounts using Windows Integrated Authentication. As you probably already discovered, when creating the domain account linkage in Solarwinds you define the account as "domain\user". Defining a password actually isn't necessary.

If you want to use a local account it's slightly different but the concept remains the same. Create a Windows account on the Orion server. When creating the Orion linkage on the Web make sure the user name is "OrionServerName\username". Again, defining a password in Orion is optional.

When your user goes to access Orion they will need to enter their user name as "OrionServerName\username" and use the password that was defined when creating the local windows account on the Orion server.

vhcato

That's interesting. I've never had to prepend "OrionServerName\" to my local user accounts, and it's working for me..?

aLTeReGo

IIS will always default to the local computer for authentication if no domain is specified in the username string. Technically you shouldn't need to manually specify the machine name in the logon credentials since this is what's happening transparently in the background anyway but I find it good technical etiquette since it eliminates any potential guesswork as to what's going on.

vhcato

Gotcha...