Home > Forum > Installation > 401 error Unauthorized while trying to log in

401 error Unauthorized while trying to log in
0

Problem with launching the WEBCON portal after a new installation according to the instructions "WEBCON BPS standalone installation" (windows 2025 and updates, .NET Framework 4.7.2, installed automatically with the system, ASP.NET Core Runtime 8.0 Windows Hosting Bundle, MSSQL 2019 with installed full-text search , Ms Sql Server Management Studio 20, IIS with Windows Authentication), also tried to fix using this thread -> https://community.webcon.com/forum/thread/1042 .

When I try to log in even if I made everywhere user and password same (during installation) I still get 401 Unauthorized. It doesn't show error unless you use inspect tool. Also I use http (no SSL).

MVP

Hi Androsh,

if I noticed it correctly you are using the address http://webcon.pl for the BPS portal.

I find it strange, that you get a Windows Authentication window at all. After a new installation only the custom authentication "Admin access" is enabled and the windows authentication needs to be enabled in the designer studio afterwards.
Therefore I'm assuming, that the request does go to a different server. Did you configure the DNS or at least the hosts file on the server that webcon.pl is pointing to the server?

Btw. even if this is a local system, I advise against using an unsecured connection.

Best regards,
Daniel

WEBCON

Hi Androsh,

There is a known bug on version 2026 which makes Admin access authentication impossible if Portal is running on HTTP.
There are two workarounds:
- obtaining an SSL certificate, updating IIS bindings and Portal address to https
- configuring Active Directory as an authentication provider and user synchronization source via setup.exe -> Tools for application management, then granting your AD account admin privileges via WEBCON BPS System Administrators (see https://community.webcon.com/posts/post/admin-access/589/3 ). Restarting Workflow Service and IIS may be required in this case.

Problem should be fixed in upcoming 2026.1.3 patch.
Sorry for the inconvenience.