0 votes

In past I am able to enable Auto Logon (Windows Integrated Auth) in our Internal Adaxes Server (full server) and in same time Form based auth for DMZ Based web server (just web services).

I am trying to upgrade to 2018.2, but as all of my sub websites are replicating configuration between all web servers, If I disable Auto Logon on one, it disables everywhere. So how can I enable Auto Logon for internal server and disable for DMZ server? User should automatically login when internal network but when outside, they should get the auth form for login.

by (460 points)

1 Answer

0 votes
by (288k points)
selected by
Best answer

Hello,

Unfortunately, there is no such possibility. You will need to create a separate Web Interface that will be available only on the DMZ server and a separate Web Interface that will be available only internally. For information on how to specify on which servers a Web Interface should be available, have a look at the following tutorial: https://www.adaxes.com/tutorials_WebInt ... ervers.htm.

0

I understand this Access Control and division of web sites into multiple servers. But it is not related to what I am looking for.

So in the current version - Per Website "Auto Logon" config will be pushed to every Server, where this website is hosted.

0

Hello,

In Adaxes 2017.2 and earlier each instance of Adaxes Web Interface had its own configuration that was stored on the computer where the Web Interface was installed. As a result, you could have Adaxes Web Interface installed on different computers having Web Interfaces with the same names and different configurations.

Starting with Adaxes 2018.1, the Web Interface configuration is stored on Adaxes backend together with the service configuration. As a result, you can have only one Web Interface with a unique name. There is no possibility to create Web Interfaces with same names no matter how many instances of Adaxes Web Interface you have installed.

That is why, you will need to create two Web Interfaces with different names. One will be available only on the computer in the DMZ and have Auto Logon disabled, the other will be available only on internal computers and will have Auto Logon enabled.

Related questions

0 votes
1 answer

Hi, We are currently still running an older version of Adaxes (2014.1) and having an issue with our 2nd server of Adaxes that is in our DMZ. I would like to resolve this ... done to the environment. I am wondering if I can get any assistance on this. Thanks,

asked Jun 6, 2017 by Kobe46 (390 points)
0 votes
1 answer

We are in the process of upgrading from Adaxes 2014.1 to Adaxes 2018.2. In our current architecture we have the web interfaces deployed to their own websites in IIS. ... like to set distinct URLs for each web interface. Thanks in advance for any assistance.

asked Feb 11, 2019 by lgibbens (320 points)
0 votes
1 answer

Are charts supposed to be "clickable"? They are a nice overview but provide little value unless a user is able to drill-down into the charted information. Example ... we've upgraded from 2016. Just getting clarification on the functionality here. Thanks, Dave

asked Nov 8, 2018 by VTPatsFan (610 points)
0 votes
1 answer

Since upgrading to 2018.2 we are experiencing an issue where the Softerra.Adaxes.Service will consume all of the OS's available memory causing it to become unresponsive. ... for the service or figure out what might be causing the high memory utilization?

asked Nov 2, 2018 by yourpp (540 points)
0 votes
0 answers

Adaxes 2018.2 has arrived and is available for download! Parameters for Custom Commands. Managing individual Office 365 services. And more. Check out what's new in the ... Follow the Upgrade Instructions: https://www.adaxes.com/resources/releas ... tNotes.htm

asked Oct 18, 2018 by Adaxes (560 points)
3,538 questions
3,229 answers
8,224 comments
547,747 users