This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How handle AD SSO & Basic-Authentication?

Hello,

I've configure a web-proxy profile for my client network with AD SSO (standard mode). This works greate. But one department has an application wich require a manual proxy configuration with username & password. But it does not support NTLM. So the application sends basic-auth wich are declined by the webfilter, because it's running in AD SSO.

So, how can I implement something like "if AD SSO does not work, try basic-auth"?

Thanks in advance,
Funny

This thread was automatically locked due to age.

Parents

0 BAlfson over 12 years ago

Funny, in your GPO for 'Proxy Settings', are you using the IP of "Internal (Address)" or an FQDN that resolves to that IP?

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 12 years ago

Funny, in your GPO for 'Proxy Settings', are you using the IP of "Internal (Address)" or an FQDN that resolves to that IP?

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 FunnyDingo over 12 years ago in reply to BAlfson

I'm using the FQDN. Is there a difference in using FQDN and IP?
Cancel
Vote Up 0 Vote Down

Cancel
0 matthias.schmidt over 12 years ago in reply to FunnyDingo

I'm using the FQDN. Is there a difference in using FQDN and IP?

For WEB Browsers there is a difference. They will use Kerberos if there is a FQDN and NTLM if there is a IP.
But i doubt that your Applications will handle it differently.
Cancel
Vote Up 0 Vote Down

Cancel