Hi,
We just need to use the AD domain server as a user database to authenticate
users according to the domain sets IQP admin desires. I believe there should
be a way to connect to AD directory server and ask if
domain\usern...@password is valid or not! (the syntax may be different but I
guess you
Fastream Technologies wrote:
Hi,
We just need to use the AD domain server as a user database to
authenticate users according to the domain sets IQP admin desires. I
believe there should be a way to connect to AD directory server and
ask if domain\usern...@password is valid or not! (the
On Sat, Dec 18, 2010 at 6:49 PM, Arno Garrels arno.garr...@gmx.de wrote:
Fastream Technologies wrote:
Hi,
We just need to use the AD domain server as a user database to
authenticate users according to the domain sets IQP admin desires. I
believe there should be a way to connect to AD
Fastream Technologies wrote:
On Sat, Dec 18, 2010 at 6:49 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
Hi,
We just need to use the AD domain server as a user database to
authenticate users according to the domain sets IQP admin desires. I
believe there
Alright. Let's say there are two virtual servers, one per domain on the
ICS
web server. For example in OnGetDocument, you assign different
TFileStream's
to different FRequestHost's. I need each HTTP domain's user set to
authenticate against a different AD/NTLM domain. It will be the
Let's say the web server is listening on the IP 192.168.2.2. A virtual
server is an Apache term for two domains on the same IP such as
www.domain1.com and www.domain2.com . We want people who log on to domain1
to be authenticated against NTLMdomain1 and domain2 to NTLMdomain2. These
should be
Fastream Technologies wrote:
Let's say the web server is listening on the IP 192.168.2.2. A virtual
server is an Apache term for two domains on the same IP such as
www.domain1.com and www.domain2.com . We want people who log on to
domain1 to be authenticated against NTLMdomain1 and domain2 to
Hi Arno,
On Fri, Dec 17, 2010 at 12:22 PM, Arno Garrels arno.garr...@gmx.de wrote:
Fastream Technologies wrote:
Let's say the web server is listening on the IP 192.168.2.2. A virtual
server is an Apache term for two domains on the same IP such as
www.domain1.com and www.domain2.com . We
Fastream Technologies wrote:
Hi Arno,
On Fri, Dec 17, 2010 at 12:22 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
Let's say the web server is listening on the IP 192.168.2.2. A
virtual server is an Apache term for two domains on the same IP
such as
Anybody else who need this feature want to be a sponsor for it? As I said we
offer $180 if it could be completed until January 1st.
Regards,
SZ
On Wed, Dec 15, 2010 at 5:59 PM, Maurizio Lotauro
lotauro.mauri...@dnet.itwrote:
Scrive Arno Garrels arno.garr...@gmx.de:
Arno Garrels wrote:
Fastream Technologies wrote:
Anybody else who need this feature want to be a sponsor for it? As I
said we offer $180 if it could be completed until January 1st.
Anybody else who need this feature want to be a sponsor for it? As I said we
offer $180 if it could be completed until January 1st.
Sorry for the confusion. I meant there should be a new event with a
reference String variable which would be set by the application programmer
to set the NTLM domain before the NTLM message 1 is sent. Or maybe there
could just be a new String property which would be null by default (for the
Fastream Technologies wrote:
Sorry for the confusion. I meant there should be a new event with a
reference String variable which would be set by the application
programmer to set the NTLM domain before the NTLM message 1 is sent.
Or maybe there could just be a new String property which would
Dear Arno,
I was talking about the web server but the client also needs some mechanism
to indicate the NTLM domain so that it can send request to the web server in
case of NTLM on the web server. But wait a minute, when there is reverse
proxy sitting in front, web servers cannot authenticate with
So since we are talking about the web server, the NTLMDomain property should
be of THttpConnection, NOT the THttpServer. In the OnGet/Head/PostDocument
it should be set by the app coder or if it is not set then it will be null
hence work as it is now.
Regards,
SZ
On Thu, Dec 16, 2010 at 4:15
Fastream Technologies wrote:
So since we are talking about the web server, the NTLMDomain property
should be of THttpConnection, NOT the THttpServer. In the
OnGet/Head/PostDocument it should be set by the app coder or if it is
not set then it will be null hence work as it is now.
I was
Hello,
On Thu, Dec 16, 2010 at 5:00 PM, Arno Garrels arno.garr...@gmx.de wrote:
Fastream Technologies wrote:
So since we are talking about the web server, the NTLMDomain property
should be of THttpConnection, NOT the THttpServer. In the
OnGet/Head/PostDocument it should be set by the app
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 5:00 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
So since we are talking about the web server, the NTLMDomain
property should be of THttpConnection, NOT the THttpServer. In the
Hello,
On Thu, Dec 16, 2010 at 7:04 PM, Arno Garrels arno.garr...@gmx.de wrote:
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 5:00 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
So since we are talking about the web server, the NTLMDomain
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 7:04 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 5:00 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
So since we are talking about the
On Thu, Dec 16, 2010 at 7:51 PM, Arno Garrels arno.garr...@gmx.de wrote:
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 7:04 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 5:00 PM, Arno Garrels
Personally I never needed such feature but customers who use reverse proxy
as SSL VPN they say they need it.
Is it possible for you the clearly defines the requirements, not in terms of
your own application, but in terms of HTTP client and server components ?
Describe why and how the current
Each URL Rule should be able to authenticate against a configurable AD
domain!
This is not ICS component language. Please translate this into client or
server component behaviour.
Be clear about which component you talk about.
--
francois.pie...@overbyte.be
The author of the freeware
Fastream Technologies wrote:
On Thu, Dec 16, 2010 at 7:51 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 7:04 PM, Arno Garrels arno.garr...@gmx.de
wrote:
Fastream Technologies wrote:
Hello,
On Thu, Dec 16, 2010 at 5:00 PM,
Hello,
Alright. Let's say there are two virtual servers, one per domain on the ICS
web server. For example in OnGetDocument, you assign different TFileStream's
to different FRequestHost's. I need each HTTP domain's user set to
authenticate against a different AD/NTLM domain. It will be the
Scrive Arno Garrels arno.garr...@gmx.de:
Arno Garrels wrote:
Arno Garrels wrote:
Maurizio Lotauro wrote:
Scrive Arno Garrels arno.garr...@gmx.de:
Looks like it's not possible with current THttpCli:
[...]
Have you tried adding the domain to the name as dom...@user?
Sometime
Arno Garrels wrote:
Arno Garrels wrote:
Maurizio Lotauro wrote:
Scrive Arno Garrels arno.garr...@gmx.de:
Looks like it's not possible with current THttpCli:
[...]
Have you tried adding the domain to the name as dom...@user?
Sometime I need to do so to get it working.
That doesn't
So it still needs some work before the beta testing. AFAIU, if it is just
one message to be modified, then it should not be much difficult to write a
generic code to cover all NTLM versions.
SZ
On Tue, Dec 14, 2010 at 10:22 AM, Arno Garrels arno.garr...@gmx.de wrote:
Arno Garrels wrote:
Arno
28 matches
Mail list logo
